Articles I've written
Is Documentation Really Wasted Effort?
A widespread myth I've noticed in Agile software development is, "No documentation in Agile" or "Documentation is wasted effort." Particularly during a transition from Waterfall to Agile, we appreciate the benefits of adopting typical Scrum practices, such as short iterations, timeboxing, daily scrums, retrospective, and so on. We also try to get away from the tasks and activities that we found monotonous before Agile adoption — documentation, writing proper code comments, etc. But is it really correct to completely stop documentation and code comments?