Committing to the Sprint Backlog
As we discussed in Chapter 10, Sprint Planning, the sprint planning event is where the whole Scrum team gathers to define the work for the next sprint by creating a sprint goal, a sprint backlog, and a forecast. At the end of this event, the development team should have a plan for the first few days of the sprint that details how they believe they can accomplish the sprint goal. That plan is in the sprint backlog (flip back to the intro of this chapter for details of what should be in this plan.) But many organizations insist on a more robust plan that leaves little or no room for change.
We frequently hear Scrum teams and organizations say that the sprint backlog is a commitment—that everything in the sprint ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access