We use TFS and the project template ScrumForTeamSystem . Our Task Board for Scrum is so digitally. We meet every day around a 24 "monitor and push our digital task list via task board . The Burn Down Charts of the sprint is determined from AUTOMATIC.
other day I had with a colleague, the scrum does not know, an interesting discussion. The impetus of the discussion was to look at our current and past Burn Down Charts
The question. "Why the soaked your progress in the burn-down charts from as much by the plan?" and "Why are you planning to sprint not that the Is curve on the plan curve is?"
top three examples of burn down charts are shown. Where the red represents curve the wrong plan? "Frittered away" the team even takes the time and nothing done?
What would it mean exactly to a team green curve to trim down? We developers would build into our cost estimates, simply enough buffer. We want to go then yes absolutely certain that we stay in the time frame of the plan curve. Now may be that they need that buffer. More likely, however, that they do not need it. This means that plug into a green curve is a lot of time reserves. In a Red but no.
Conclusion: Too smooth burndown charts can only be achieved with enough time reserves.
0 comments:
Post a Comment