Read about the experiences and ideas of Agile colleagues around the world, and share your own thoughts here. You can also visit
, which features blogs by experts in the fields of Scrum, Agile, and the broader business world.
8/10/2017 by Anurag Prakash
I believe that task estimation in Agile is starting to lead to a series of problems.
7/5/2017 by Anurag Prakash
With the number of books, blogs, and articles out there, one would assume that Agile transformations have become a science. It’s surprising to see the number of failures in Scrum adoption. A common reason is the unavailability of essential ingredients for success.
4/19/2017 by Anurag Prakash
The burn-down has exploded in popularity as a tool for tracking the team's activities, but I have found quite a few misuses of burn-downs.
2/13/2014 by Anurag Prakash
SOA enables agility as compared to a monolithic software solution or other tightly coupled approaches. . . .
12/10/2013 by Anurag Prakash
Waterfall probably came about with all good intentions. In some ways it mimics layered software architecture: Interface between the adjacent layers is clearly defined. There is clean delineation of responsibility. . . .
10/22/2013 by Anurag Prakash
How do we deal with bugs in Scrum? Do we size them? Do we add them to a separate backlog? Or do we assign them to a different team running Kanban?
10/2/2013 by Anurag Prakash
Scrum is easy to learn but difficult to implement, as has often been said. Everyone I have met has had tons of issues, from how to size a story to "Oh, we have a constant stream of bugs." Let's examine broad categories of issues.
9/19/2013 by Anurag Prakash
Teams new to Scrum frequently push back on the Scrum rituals and the updates. The most painful of these is updating hours left. . . .
9/4/2013 by Anurag Prakash
The idea of Sprint Zero, like a lot of other things, has been used and abused. . . .
6/12/2013 by Anurag Prakash
For effective Scrumming, stories should have the desirable INVEST characteristics: They should be independent, negotiable, valuable, estimable, sized, and testable). We'll assume that the product owner is trained in Scrum and creates clean stories...