Lean-Agile
Coaching and Training
Other
-
- Also some Useful Tools
Note that we have some Incomplete Pages That Require Work on this site:-)
Note that we have some Incomplete Pages That Require Work on this site:-)
The purpose of Iteration (Sprint) Planning is to allow the Team to commit to what they can deliver in the next Iteration (Sprint) - the committed Team (Sprint) Backlog.
Iteration (Sprint) Planning occurs at the beginning of the Iteration (Sprint), after you have completed the Iteration Demo (Sprint Review) and Retrospective of the current Iteration (Sprint) (i.e. the Iteration Demo (Sprint Review) and Iteration (Sprint) Retrospective are an input to the Iteration (Sprint) Planning). Note that there is typically no gap between the end of one Iteration (Sprint) and the start of the next Iteration (Sprint). (See What Events Should We Put in Place For Iterations (Sprints)? for more information.)
Iteration (Sprint) Planning may be divided into two sessions, be conducted as one session, or occur as a series of shorter incremental sessions. Typically, Iteration (Sprint) Planning is viewed as having two parts:
By the end of Iteration (Sprint) Planning 2, all Team members should be confident that the worked committed to can be completed by the end of the Sprint or have identified the risks associated with any items about which there are doubts.
The Team should use the data they have to help them make good commitments. For example, during the Iteration (Sprint) Planning 1 process the team will have velocity or throughput information to help them understand how much they can complete as a Team. By keeping a running total of the points a Team thinks it can work in the upcoming Iteration (Sprint), and comparing it to the “normal” velocity of the Team, the team can easily gauge whether they are over-committing.
Similarly when the Team gets to Iteration (Sprint) Planning 2, comparing a running total of the estimated hours on the tasks to a total team capacity for planning purposes will help the team understand what is truly possible to commit to.
Purpose: Determine what the Team should build in the next Iteration (Sprint).
Who: Team - Team, Scrum Master, Product Owner and other stakeholders as required.
Duration: Maximum 2 hours for a 2 week sprint (10 working days).
Summary Agenda:
Result: A list of backlog items that are candidates for delivery in the next Iteration (Sprint), sometimes called the Selected Backlog.
Purpose: How are we going to meet Iteration (Sprint) goals?
Who: Scrum Master and the Team, with the Product Owner at least available to answer question if not fully engaged.
Duration: Maximum 2 hours for a 2 week sprint (10 working days).
Summary Agenda:
Result: Recorded Iteration (Sprint) Backlog against which the Team has committed to complete by the end of the Iteration (Sprint).
Iteration (Sprint) Backlog
The Iteration (Sprint) Backlog is the result of Iteration (Sprint) Planning. It represents two things:
For different Teams, the level of detail tracked in the Iteration (Sprint) Backlog depends on the Team. The key information is that the Team makes a commitment, and that commitment is knowable to all stakeholders.
Deliverable
At a minimum, the Iteration (Sprint) Backlog is a list of Product (or Team) Backlog Items that the Team has committed to deliver in the Iteration (Sprint) and the basis of the information required to generate the Iteration (Sprint) Burn-down chart. For new Teams, in most cases this is a detailed plan of tasks the Team expects to undertake to meet their commitment. This detailed plan is created and tracked by the Team.
Selected Team (Product) Backlog is well prepared for the Iteration (Sprint) Planning 2.
Iteration (Sprint) Goal and Iteration (Sprint) Backlog are visible to everyone within the organization. The tasks in the Sprint Backlog are accessible to all team members.