I delight in the realization a new team member has when task estimates do not equate to actual clock hours.
Task Estimates != Sprint Time
In the activity of updating the sprint burndown chart, a team-mate notes that the sprint contains 3 to 5 times the amount of work hours as our accumulated task estimates. Wonder where all that extra time is spent? This epiphany occurs because I require the team to calculate and hand draw the team's sprint burndown chart.
Immediately after stand-up someone (an unassigned, expectation upon the team) does the task of updating the chart. They calculate the task effort remaining for all unfinished stories and update the burndown chart. I am delighted when she notes that the sprint has 2 weeks for 5 people, meaning 2 X 40 hours X 5 people = 400 effort hours per sprint. Yet we are only estimating and accomplishing something like 130 - 200 effort hours over the last several successful sprints.
See Also:
What is an Agile Transition Guide?
Task Estimates != Sprint Time
 |
| Task Hours vs Day of Sprint - Burndown Chart |
Immediately after stand-up someone (an unassigned, expectation upon the team) does the task of updating the chart. They calculate the task effort remaining for all unfinished stories and update the burndown chart. I am delighted when she notes that the sprint has 2 weeks for 5 people, meaning 2 X 40 hours X 5 people = 400 effort hours per sprint. Yet we are only estimating and accomplishing something like 130 - 200 effort hours over the last several successful sprints.
See Also:
What is an Agile Transition Guide?
Comments