How to Manage the Sprint Backlog

Introduction The Backlog is the term used for the list of requirements in Scrum and other Agile development methods.  Usually the requirements are stated in the form of an User Story or an Epic, which is a very brief explanation about what is needed.
There are three different Backlogs.

  • The Business Backlog – used to store all requirements to a specific product or system.
  • The Release Backlog – is a subset of the Business Backlog, selected for implementation in a Release.
  • The Sprint Backlog – is a subset of the Release Backlog, selected for implementation in the Sprint.

Here we focus on the Sprint Backlog!
Who is involved? Working with the Sprint Backlog involves different people with these responsibilities:

Business Product Owner Development Team Users O&M Team
Select User Stories and
Epics from the Release Backlog		 I A/R C I I
Manage Changes to the
Sprint Backlog		 C A/R C I I
Legend: R=Responsible; A=Accountable; C=Consulted; I=Informed

What is the input? The input to the Sprint Backlog is the Release Backlog.
Which tasks are expected? The following tasks is expected:

Task Description
Select User Stories and Epics from the Release Backlog The Scrum Team select the User Stories and Epics for implementation in a Sprint during the Sprint Planning.
The selected User Stories and Epics is the Sprint Backlog and is maintained under strict change control during the Sprint by the Product Owner.
Manage changes to the Sprint Backlog The basic rule in Scrum is that the Sprint Backlog cannot be changed. If change is urgently needed, the request is made to the Product Owner!
The Product Owner consult the Development Team and business in order to assess the risk and the impact the change represent to the Sprint Goal.
Based on the impact of the change, it might be necessary to remove a User Story from the Sprint Backlog in order to ensure sufficient resources to implement the change.

The Development Team has the final saying in the decision to accept or reject the change request as they are the ones committed to do the work.

How shall the result be Controlled The Sprint Backlog is under strict change control of the Product Owner after the Scrum Team has agreed to the content at the end of the Sprint Planning session.
What is the output? The output is a well maintained Sprint Backlog which is the single source of requirement for the Sprint.
When can we exit? The process do stop when the Sprint is completed.
Hints and Examples The …
…