Analyzing the Sprint 7 Burn-Down Chart
The provided image is a “Sprint 7 Burn-Down Chart” that visually represents the progress of work during Sprint 7. It includes key metrics such as remaining work hours, actual hours worked, and completed tasks.
Exam Question
Based on “Sprint 7 Burn-Down Chart” would you do anything different in Sprint 8?
(choose the best two answers)
A. There is nothing wrong. The Developers will present all Product Backlog items selected for Sprint 7 at the end of the Sprint.
B. The Developers may forecast less overall work in Sprint 8.
C. Stakeholders will encourage the Scrum Team to estimate better during the Sprint 8 Planning Meeting.
D. The Developers re-estimate incomplete Product Backlog items and put them back into the Product Backlog for re-ordering. The Product Owner may ask the Developers to complete the unfinished Product Backlog items from Sprint 7 in Sprint 8.
E. The Scrum Master adds additional Developers for Sprint 8.
F. The Developers carryover incomplete Sprint Backlog items from Sprint 7 to Sprint 8 and monitor the Sprint 8 burn-down chart. As soon as deviation from trends is detected, the Developers work with the Product Owner to negotiate remaining work.
Correct Answers
B. The Developers may forecast less overall work in Sprint 8.
D. The Developers re-estimate incomplete Product Backlog items and put them back into the Product Backlog for re-ordering. The Product Owner may ask the Developers to complete the unfinished Product Backlog items from Sprint 7 in Sprint 8.
Explanation
Correct Answers
B. The Developers may forecast less overall work in Sprint 8:
The burn-down chart shows that the Developers were not able to complete all the work planned for Sprint 7. As a result, they should consider forecasting less work for Sprint 8 to ensure that they can complete the planned work within the Sprint timebox.
D. The Developers re-estimate incomplete Product Backlog items and put them back into the Product Backlog for re-ordering. The Product Owner may ask the Developers to complete the unfinished Product Backlog items from Sprint 7 in Sprint 8:
Incomplete work from Sprint 7 should be re-estimated and placed back into the Product Backlog. The Product Owner can then re-order these items and, if deemed valuable, prioritize them for completion in Sprint 8.
Why the Other Options Are Less Appropriate
A. There is nothing wrong. The Developers will present all Product Backlog items selected for Sprint 7 at the end of the Sprint:
This is incorrect because the burn-down chart indicates that not all tasks were completed, which implies there is an issue with work estimation or execution that needs to be addressed.
C. Stakeholders will encourage the Scrum Team to estimate better during the Sprint 8 Planning Meeting:
While better estimation is important, this is not a direct action that the Scrum Team should take based on the burn-down chart. The focus should be on the Developers adjusting their forecast and re-estimating incomplete items.
E. The Scrum Master adds additional Developers for Sprint 8:
Adding additional Developers is not a recommended practice in Scrum as it disrupts team cohesion and dynamics. The focus should be on improving the current team’s estimation and execution practices.
F. The Developers carryover incomplete Sprint Backlog items from Sprint 7 to Sprint 8 and monitor the Sprint 8 burn-down chart. As soon as deviation from trends is detected, the Developers work with the Product Owner to negotiate remaining work:
Simply carrying over work without re-estimation and re-ordering does not address the root cause of the issues observed in Sprint 7.
Relevance to the PSD Exam
Understanding how to interpret burn-down charts and adjust Sprint planning based on past performance is essential for the Professional Scrum Developer (PSD) exam. This question tests the candidate’s ability to use empirical data to improve future Sprint outcomes.
Key Takeaways
- Burn-down charts provide valuable insights into the progress of work within a Sprint.
- Re-estimation and re-ordering of incomplete work are important steps to ensure that the team can deliver valuable Increments in future Sprints.
- Adjusting the forecast based on past Sprint performance helps the Scrum Team to commit to realistic goals.
Conclusion
Using burn-down charts to guide Sprint planning is a key practice in Scrum. It helps the Scrum Team make informed decisions about work forecasts and backlog prioritization. For more information on preparing for the PSD exam, visit our Professional Scrum Developer PSD™ Exam Prep.
