Tracking progress: burndown charts and velocity are two essential tools for Scrum teams. They help you see how work is moving and if your team will meet its goals. Both tools give a clear view of the sprint and project progress, which is useful for team members, Scrum Masters, and stakeholders. A burndown chart shows the amount of work left in a sprint or project over time. The vertical axis shows the work remaining, usually in story points or hours. The horizontal axis shows the days in the sprint or project. As the team completes work, the line on the chart drops down, “burning down” the work until it reaches zero at the sprint end. Burndown charts help teams quickly spot if they are on track. If the line is above the ideal burndown line, the team is behind schedule. If below, they are ahead. This lets teams adjust their work or focus to finish on time. Velocity is the average amount of work a team completes in a sprint. It is usually measured in story points. To find velocity, add up all the story points completed in recent sprints and calculate the average. This number helps teams forecast how much work they can take on in future sprints. Knowing velocity supports planning. For example, if your team’s velocity is 30 story points per sprint, then your next sprint should not have more than 30 points. This creates realistic goals and avoids overcommitting. Here are key points to understand burndown charts and velocity:
Putting tracking progress: burndown charts and velocity into practice is easy. Use your Scrum tool or a simple Excel sheet to create a burndown chart. Update it every day with completed work. Calculate velocity after each sprint to understand your team’s pace. Together, these tools help you keep everyone on the same page and deliver work successfully. They also encourage the team to inspect and adapt by showing real progress data. Remember, burndown charts and velocity are guides, not strict rules. Use them to support good decision-making and continuous improvement in your Scrum team.
Live Scenario • Active Situation
You are the Scrum Master in a software development team preparing for the sprint review.
There is no single perfect answer. Choose what you would do in this situation.