The Scrum Burndown chart is very simple tool to monitor the project status. It is easy to explain, easy to understand. But this metric also put in evidence some pitfalls observed in many agile workshops and adoptions. This article discusses how to build a Scrum burndown chart and what should be included in it. It also presents guidelines on how to assess the project status using the burndown chart and what could be done when problems are detected.
When properly implemented, the Scrum framework enforces simple constraints that lead a team to self-organize into a state that achieves 5 to 10 times performance improvement versus traditional approaches. However, the majority of Scrum teams is unable achieve this objective.
Velocity is killing agility is the observation discussed by Jim Highsmith in this blog post. He explains that this metric is increasingly used for the wrong reasons: measuring productivity and focusing on volume delivery instead than on quality. He concludes saying that the importance given to velocity should be balanced with other metrics like feature value, feature delivery cycle time or quality.
In this blog post, Sten Johnsen discusses the impact of moving uncompleted user stories from one Scrum sprint to another. He focuses on the unfinished user stories, its impact on the team velocity and its influence on the ability of the team to change.
This article discusses several symptoms and causes of schedule flaws, presents metrics and diagrams that can be used to track your team’s progress against its schedule and describes how Agile can address project management risks.
Keith Cerny presents in this blog post, metrics that could be used to measure agile teams performance.
Scrum Expert Copyright © 2009-2024 Martinig & Associates