Slide 14
Slide 14 text
@AgileCanuck
@PrettyAgile #notrainwrecks
Planning Context
19
© Scaled Agile, Inc.
Planning requirements
20
© Scaled Agile, Inc.
Team deliverables – detail
4 If a Story has a dependency, put a red
sticky on it describing the dependency.
Put a check mark through it once the
dependency has been addressed.
4 If a risk is broader in nature,
put it on the risk sheet
4 If needed, allocate a percentage of
capacity for unplanned activities like
maintenance and production support
4 The last Iteration will be used for
Innovation and Planning (IP)
4 You should have a capacity but not a
load on the IP Iteration, since it should
not contain any user value stories
4 PI Objectives should be written as
‘SMART’ objectives
4 Objectives are assigned business value
during the second team breakout
4 Stories supporting uncommitted
objectives are included in the load
calculation
4 Program risks are those that need to be
escalated to the program level. They
will be captured and ‘ROAMed’ after the
final plan review.
4 Team risks are those under the team’s
control. They won’t be presented.
Iterations Capacity____
Load____
Iteration 1.5
Capacity____
Load____
X
IP Iteration