- The Agile Developer's Handbook
- Paul Flewelling
- 171字
- 2021-06-24 18:47:20
Burndowns
At the end of Sprint Planning, after the team has broken down User Stories into tasks, the Scrum Master totals up the number of tasks in the Sprint Backlog. The Scrum Master then creates a Burndown chart.
The following diagram shows a Burndown for a Sprint already in progress:

The y-axis represents the total number of tasks. The x-axis represents the number of days in the Sprint.
The red line on the following Sprint Burndown chart represents the number of tasks left to complete.
The dotted line represents the Ideal Burndown rate in order to complete all tasks by the end of the Sprint; as you can see in the preceding figure, the red line (the Actual Burndown) hasn't decreased in the way we expected.
In this case, the Actual Burndown shows that new tasks were discovered when the team began working on a User Story, and so the total number of tasks has increased. It is not unusual to uncover new information once work commences.
- RCNP實驗指南:構(gòu)建高級的路由互聯(lián)網(wǎng)絡(luò)(BARI)
- 物聯(lián)網(wǎng)安全(原書第2版)
- Spring Boot 2.0 Projects
- Hands-On Chatbot Development with Alexa Skills and Amazon Lex
- 物聯(lián)網(wǎng)時代
- Mastering JavaFX 10
- 智慧光網(wǎng)絡(luò):關(guān)鍵技術(shù)、應用實踐和未來演進
- 網(wǎng)絡(luò)安全應急響應技術(shù)實戰(zhàn)
- Microsoft Dynamics CRM 2011 Applications(MB2-868) Certification Guide
- Unity Artificial Intelligence Programming
- Master Apache JMeter:From Load Testing to DevOps
- 6G:面向2030年的移動通信
- Hands-On Bitcoin Programming with Python
- Qt5 Python GUI Programming Cookbook
- 智慧城市中的物聯(lián)網(wǎng)技術(shù)