- 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.
- 網絡教育學習指導
- Mastering Machine Learning for Penetration Testing
- 網絡故障現場處理實踐(第4版)
- Hands-On Full Stack Development with Spring Boot 2 and React(Second Edition)
- 網絡互聯技術(實踐篇)
- SD-WAN架構與技術(第2版)
- 通信簡史:從信鴿到6G+
- Working with Legacy Systems
- 6G:面向2030年的移動通信
- 語音信號處理及Blackfin DSP實現
- 網絡綜合布線(第2版)
- Learning Node.js Development
- Dart Cookbook
- Selenium WebDriver 3 Practical Guide
- Building RESTful Web Services with .NET Core