The Sprint Backlog is a list of Product Backlog Items (PBIs) the Team has committed to for the next Sprint. It is the Scrum Team’s plan for how to achieve the Sprint Goal. Since the Sprint Backlog is solely for the use of the Team to organize their own work, they are the only ones who create, change, and manage it — not a tool, and not an outsider. Since Teams are unique, there is no single correct practice that they all should follow. Teams choose and experiment with whatever helps them most to stay focused and self-organize, creating the Sprint Backlog with whatever methods work best for them, such as index cards, whiteboards, or, yes, even electronic tools.
Resource Links:
- Elements of an Effective Scrum Task Board
- Myth: The Sprint Backlog can’t change during the Sprint
- Sprint Backlog – Pattern
- Your Scrum Sprint Backlog Caveat it recommends the use of burndown charts – I don’t anymore
- What is Sprint Backlog in Scrum Framework
*Thank you for visiting the World's Largest Opinionated Agile Reference Library. This content is created and the links are curated through the lens of Agile Pain Relief Consulting's view of what is effective in the practice of Scrum and Agile. We don't accept submissions and emails to that effect are marked as spam. Book listings may use affiliate links that could result in a small commission received by us if you purchase, but they do not affect the price at all. From experience, this won't amount to anything more than a cup of coffee in a year.
