We're looking at Scrum in detail. Today it's the turn of the SPRINT BACKLOG.


= = = = = = = = = = = =

New for 2024: my best-ever training:
"How Your Agile Teams Can Achieve Predictability and Productivity WITHOUT Burnout"
→ https://www.developmentthatpays.com/w...

= = = = = = = = = = = =

Grab your FREE Scrum Cheat Sheet: https://www.developmentthatpays.com/c...





-------------------
133. Sprint Backlog + FREE Cheat Sheet
#SprintBacklog #AgileScrum #DevelopmentThatPays

The Sprint Backlog is the list of things that the Development Team that the development team will work on during the sprint. It is created once for every Sprint. And Sprint Planning is the Scrum Event where it is created. The Product Backlog - the “master list” of things to do - provides the input. Simply put - and I’m quoting directly from the Scrum Guide here - “The Sprint Backlog is the set of Product Backlog items selected for the Sprint” Two properties of the Product Backlog and its contents are important/relevant/helpful when it comes to making the selection. It is a prioritied list - the most valuable items are at the top. And the items - at least those towards the top of the list - are “sized”. It’s common practice to size with Story Points - though You won’t find them mentioned in the Scrum Guide. And if the Team has a few Sprints under its belt. It will have some idea of its CAPACITY The number of Story Points it can handle - process - during the course of a Sprint. Could it be that Sprint Planning is as simple as Taking items one at time from the top of the Product backlog …. Until the total number of Story Points selected…. equals the Capacity. Perhaps with a bit of jiggling at the end to fill the last space. If it were that simple, there’s be a button for it in Jira. // And perhaps there is. I’ve no idea!! Let’s take half a step back and begin with the end in mind By the END of the Sprint, the Development Team’s job is to develop/produce/create an Increment. To give it its Sunday Name: a potentially releasable increment. So - as far as it is possible - it make sense that the selected Product Backlog Items are complementary. Coherent. All - in some way - pulling in the same direction. Towards…. an agreed Sprint Goal. The Scrum Guide ties these the things together nicely: “The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.”
   • Sprint Backlog + FREE Cheat Sheet