Tuesday, September 22, 2009

Needless time tracking in Scrum

On a new assignment, while the client is trying to slowly adopt Scrum (and hence Agile), I have been bothered by the needless time tracking that is proposed by some of the Scrum templates and related literature .

Tracking hours remaining at a task level, or even %age task completion to me is useless. Either a user story is done or not done, simply because you cant do much with a half baked story. A story which is done contributes to the velocity or throughput. Everything else is inventory.


  1. AGREEEEEE!!!!!! It is a silly practice.

  2. I think you need to read some more about scrum to have a better understanding of what you are commenting on. Though it's a safe bet what you are seeing is a poor or incorrect implementation of scrum

  3. I'm a Certified ScrumMaster (2003) and a practitioner of XP for at least that many years. Tracking hours like that is a waste of time. In fact, I'll go as far to say that tracking anything other than OUTPUT is a waste of time.

  4. Daily estimation updates during the sprint is quick (=low cost) and THE input to the burndown (=high value). The burndown helps us (the team) to see, very early on, if we are on track or not.

    So for us it is a HighValue/LowCost, and thus not waste.