💡 The Sprint Backlog is the list of all of the work the team plans on doing in the Sprint.
Key characteristics #
The Sprint Backlog (SB) is created in the Sprint Planning and includes the Sprint Goal, the Product Backlog items selected for the Sprint, and the tasks to be completed in order to get to the Sprint Goal.
The SB can and will change during the Sprint as more is discovered when the team works on the items selected. The team doesn’t have to have all of the details planned out for every Sprint Backlog item in the Sprint Planning.
The Sprint Backlog is owned by the Developers. They can make any changes in the Sprint Backlog they see fit, however, they should keep these changes visible and actively communicate with the Product Owner about them.
The SB should be kept visible to everyone involved in the product development (including the stakeholders) and always up-to-date.
Example #
For example, when building an online store the Sprint Backlog may look like this after the Sprint Planning.
Product Backlog item #1 #
Create a landing page for product N.
- Sources the product images
- Write the description
- Create a page structure
- Insert the text and the images
- Test that the page is properly displayed
- Review the texts for any spelling mistakes
- Verify the page speed to be under 3 seconds
Product Backlog item #2 #
Integrate a PayPal button for one item purchase for product N.
- Register for a corporate PayPal account
- Complete all account verifications to enable payments
- Create the code snippet for the button
- Insert the button into the product landing page
- Run an end-to-end test
Commitment: Sprint Goal #
The commitment associated with the Sprint Backlog is the Sprint Goal.
