Task identification in burndown
It would be nice to have some way to identify task that cause a peak on the burndown chart (could be something like per story burndowns...). Since this mainly comes from new tasks being identified or old tasks needing more time than expected, a feature like this would help to identify were additional working power is required.
Issue is closed.
Wed, Mar 14, 2012, 18:05 by artjom (PO,T)
I am not convinced by this idea. Our general guideline says to not include metrics that distract from the central Scrum metrics: Sprint Burndown and Velocity.
Now, introducing such an identification of Tasks within the Sprint Burndown would also be a serious challenge, UI wise.
What I cannot see is the actual gain from such a feature (that outweights the disadvantages in cluttering the UI and investing the implementation effort).
The Whiteboard already indicates how much of a Story is already done (or still needs to be done). Also, we should take into account that the Team has commited to complete all the Stories (not many or some of them), and should ideally do so from top to bottom (to avoid the case that Stories are completed in an order that contradicts their priority).
Thu, Mar 15, 2012, 04:03 by Sven
Our current situation: Developing decentralized, since I am on the other side of the world. I come home and check kunagi. What I see is that work has been done. Good. What I don't see in many cases is _where_ the work has been done. Especially when there's only time logged but no task completed, which is a serious indicator that problems occurred.
Alternative idea: make logging time an entry on the journal?
Thu, Mar 15, 2012, 10:34 by Witek (SM,T)
I am afraid this would spam the journal too much. If tasks are burned, but not closed these should be in the "Claimed Tasks" column. Do you realy have that much of them?