5-6 minutes<\/p>\n
Sprint Backlog is a set of Product Backlog items selected for the current Sprint , plus plans for delivering product increments for achieving Sprint goals . Sprint Backlog is the development team\u2019s expectation of what functions will be included in the next increment and what work will be required to deliver those functions.<\/p>\n
Scrum Sprint Backlog<\/p>\n
The Sprint Backlog defines what the development team needs to do to convert the Product Backlog Items into increments of \u201cdone\u201d. The Sprint Backlog clarifies the work required by the development team to achieve the Sprint goals.<\/p>\n
Sprint Backlog<\/p>\n
The Sprint Backlog is a sufficiently specific plan to make progress changes understandable in daily meetings . The development team will modify the Sprint Backlog throughout the Sprint, and the Sprint Backlog will gradually emerge in the Sprint process, such as the development team working according to plan and knowing more about the work needed to accomplish the Sprint goals.<\/p>\n
When a new job comes up, the development team needs to add it to the Sprint to-do list. As tasks proceed or are completed, the estimated remaining workload for each task needs to be updated. If a part of the plan loses the meaning of development, it can be removed. Within Sprint, only the development team can modify the Sprint Backlog. The Sprint Backlog is highly visible, a real-time reflection of the team\u2019s plans to complete work within the current Sprint, and it belongs only to the development team.<\/p>\n
As the Product Backlog Items are placed in the fixed Sprint cycle, the Sprint Backlog will be changed for the following reasons:<\/p>\n
Product Owner may work with Scrum Team to help Team better understand Sprint\u2019s goals. Scrum Master and Team may feel that minor adjustments will not affect Sprint\u2019s progress, but will bring more business value to customers.<\/p>\n
At any point in Sprint, the sum of all remaining work on the Sprint Backlog can be calculated. The development team tracks all remaining work at least at daily meeting sand predicts the likelihood of achieving the Sprint goals. By keeping track of the rest of the work in Sprint, the development team can manage its progress.<\/p>\n
Scrum does not consider the time spent on the Sprint Backlog. We only care about the remaining work and time variables.<\/p>\n
Sprint Burndown Chart shows the cumulative remaining workload in Sprint, which is a trend for reflecting the status of workload completion. The Y axis represents the remaining workload and the X axis represents the Sprint workday.<\/p>\n","protected":false},"excerpt":{"rendered":"