Sprint Backlog
The Sprint Backlog?is a plan by and for the Developers. It is a highly visible, real-time picture of the work that the Developers plan to accomplish.
A sprint backlog is the set of items that a cross-functional product team selects from its product backlog to work on during the upcoming sprint.
Typically the team will agree on these items during its sprint planning session. In fact, the sprint backlog represents the primary output of sprint planning.
The?product backlog?is the comprehensive list of product-related tasks that, at any given time, should encompass all of the things the cross-functional team has agreed to work on eventually, either to bring the product to market or to improve it. When these items are kept in order of priority, a product backlog should communicate which user stories, features, bug fixes, and other to-do items the development team should work on next.a
You can also think of the product backlog as a tactical, task-level breakdown of the strategic plan outlined in your?product roadmap.
With that in mind, a sprint backlog is a much shorter list pulled from the items on the product backlog — specifically, those items the team identifies during a?sprint planning meeting?as the most important tasks to complete next.
领英推荐
Here are a few key takeaways about the distinction between sprint backlogs and product backlogs, and how the two work together:
1. Sprint backlog items should be taken directly from the product backlog.
2. While the product backlog can be changed frequently at any time, according to the always-changing realities in an organization or in the market, the sprint backlog should remain as fixed as possible throughout the duration of the sprint.
3. The product team should conduct regular?product backlog grooming sessions, to ensure that sprint planning meetings are productive and that the team is able to quickly identify the right tasks to place on the next sprint backlog.
4. The top items on a well-groomed, prioritized product backlog will often represent the upcoming sprint backlog.
5. If the team is unable to complete (or even begin) certain sprint backlog items by the end of the sprint, the team might choose to add those unfinished jobs either to the next sprint backlog — if they are still deemed high priority — or to the product backlog to be addressed again in the future.