Scrum Artifacts # 2 - The Sprint Backlog
We learned yesterday there are 3 Scrum Artifacts and that each artifact contains a commitment to ensure it provides information that enhances transparency and focus.
The second Scrum Artifact is the Sprint Backlog. The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).
The Sprint Backlog is a plan by and for the Developers. No one else tells the Developers how to turn Product Backlog items into Increments of value. The Sprint Backlog is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal.
When unexpected work comes in, the backlog is flexible, however, no changes are made that would endanger the Sprint Goal or decrease value.
If unexpected work doesn't endanger the Sprint Goal, decrease the value of the increment(s) created that Sprint, or render the Sprint Goal obsolete, then the Sprint Backlog is refined as needed and the Scope clarified and renegotiated with the Product Owner, otherwise, that new work makes it way to the Product Backlog for future consideration.
The exception to this is if this new information renders the current Sprint Goal obsolete. Then, the Product Owner can cancel the Sprint so the team can start a new one with a revised Sprint Goal.
Only the Product Owner has the authority to cancel a Sprint.
The Commitment for the Sprint Backlog is the Sprint Goal. We commit to the Sprint Goal, not the Sprint Backlog, otherwise, we are committing to scope.
The Sprint Goal is the single objective for the Sprint. Not a bullet list, not a numbered list, not an i, ii, iii, iv multipart list.... it is a SINGLE object for the Sprint. The Sprint Goal is created during the Sprint Planning event and then added to the Sprint Backlog.
Have you ever spent a bunch of time on work only to be "informed" that it's the wrong direction because it wasn't clear, to begin with? How could having Scrum in place change the landscape of your development environment?
Excerpts used under CC license - https://bit.ly/38a3Osy