Sprint Charts

 

1. Velocity Chart

Explanation: The Velocity Chart shows the amount of work a team completes during each sprint. It helps in forecasting the amount of work the team can handle in future sprints. The chart typically displays the committed vs. completed story points for each sprint.

Example: Imagine your team has completed three sprints with the following story points:

• Sprint 1: Committed 30 points, Completed 25 points
• Sprint 2: Committed 25 points, Completed 20 points
• Sprint 3: Committed 28 points, Completed 28 points

The Velocity Chart would show bars for each sprint, comparing the committed story points (expected work) to the completed story points (actual work). This helps in understanding the team’s capacity and setting realistic expectations for future sprints.

2. Burndown Chart

Explanation: The Burndown Chart tracks the remaining work in the sprint backlog against the time remaining in the sprint. It helps teams visualize their progress and predict if they will complete the sprint’s work by the end date.

Example: Consider a 2-week sprint with a total of 50 story points:

• Day 1: 50 points remaining
• Day 3: 40 points remaining
• Day 5: 30 points remaining
• Day 7: 25 points remaining
• Day 9: 10 points remaining
• Day 10: 0 points remaining

The Burndown Chart would plot the remaining story points on the vertical axis and the sprint days on the horizontal axis. Ideally, the line should steadily decline, reaching zero by the end of the sprint, indicating all work is completed.

3. Burnup Chart

Explanation: The Burnup Chart shows the amount of work completed and the total amount of work in a project. It helps visualize scope changes during a sprint and the team’s progress towards completing the work.

Example: Assume a sprint with a goal of 50 story points and the following progress:

• Day 1: 0 points completed, 50 points total
• Day 3: 10 points completed, 50 points total
• Day 5: 20 points completed, 60 points total (scope increased)
• Day 7: 30 points completed, 60 points total
• Day 10: 60 points completed, 60 points total

The Burnup Chart would have two lines: one showing the cumulative completed points and the other showing the total scope. The gap between the lines indicates the remaining work. The lines should converge at the end of the sprint if all work is completed.

4. Cumulative Flow Diagram (CFD)

Explanation: The Cumulative Flow Diagram shows the status of work items over time, illustrating the amount of work in different stages (e.g., to do, in progress, done). It helps in identifying bottlenecks and ensuring a smooth flow of tasks.

Example: Consider a sprint with stages 'To Do,' 'In Progress,' and 'Done':

• Day 1: 20 tasks in 'To Do,' 0 in 'In Progress,' 0 in 'Done'
• Day 3: 15 tasks in 'To Do,' 5 in 'In Progress,' 0 in 'Done'
• Day 5: 10 tasks in 'To Do,' 5 in 'In Progress,' 5 in 'Done'
• Day 7: 5 tasks in 'To Do,' 5 in 'In Progress,' 10 in 'Done'
• Day 10: 0 tasks in 'To Do,' 0 in 'In Progress,' 20 in 'Done'

The CFD would have colored bands representing each stage, showing the number of tasks in each stage over time. The width of the bands highlights the work distribution and any potential delays or bottlenecks.

5. Sprint Report

Explanation: The Sprint Report provides an overview of the sprint, showing the completed tasks, any tasks moved to the next sprint, and details about the sprint’s progress. It’s useful for retrospective meetings to discuss what went well and what can be improved.

Example: For a sprint with 20 tasks:

• Completed: 15 tasks
• Moved to next sprint: 5 tasks
• Issues: Any blockers or impediments faced

The Sprint Report would list these details, helping the team to analyze their performance and plan for the next sprint.

6. Control Chart

Explanation: The Control Chart shows the cycle time for tasks, indicating how long it takes to complete a task from start to finish. It helps in understanding process efficiency and identifying any outliers that take longer than usual.

Example: If the team has completed tasks with the following cycle times (in days):

• Task 1: 3 days
• Task 2: 5 days
• Task 3: 2 days
• Task 4: 7 days

The Control Chart would plot these cycle times, highlighting the average time and any tasks that deviate significantly from the average. This helps in identifying inefficiencies and areas for improvement.