SAFe Lego Game for learning Scaled Agile Framework PI Planning Assigning Business Value Frequent integration

1. SAFe Lego Game
Adapted from Lego4Scrum by
Joan Nwosu - 2017

2. SAFe Lego game – Toronto City
Rules
• 1 ART
• 1 product
• 3 teams
• 1 PI – 4 sprints
• Build – integrate – review – build
• PM rates features against BV
Outcome
• Appreciate SAFe framework
• Estimate and plan for a PI
increment (2 months )
• Understand feature level
acceptance criteria
• Understand business value
• Have fun

3. Roles Rules Schedule
1 Product Manager for all teams
1 Product for all teams
 Owns product vision
 Creates program backlog
 Assigns business value
 Prioritizes the backlog
 Defines acceptance criteria
 Accepts constructs
 NOT a builder
Scrum Master (optional)
 Facilitates sprint planning,
review and retrospective
 Removes impediments (finds
Lego)
 NOT a builder
Team Member
 Builds Lego!
• Have fun
• Be creative –Use big and small pieces
• Build a lot – don’t reuse something you
already created for a new story
• Don’t steal pieces from other teams
• Use other items to enhance construct
but only Lego for building
• Integrate at the end of each sprint
• Roll a 5 and one team member goes on
compulsory vacation for half of the
sprint
• Roll a 2 and you join the another team
for the sprint
• PM will spend 1 minute per planning
session with teams clarifying
acceptance criteria
• PM will assign business value and score
accordingly
Schedule (75 mins)
10 mins: review and prioritize
backlog
PI Planning
5 min Product Vision
15 min Build the backlog
10 min Feature Estimating (BV)
2 min Feature selection
Sprints x 4
3 minutes planning
1 minute standup
7 minutes execution
1 minute integrate
3 minutes review/ demo
3 minutes retrospective

4. Toronto - features
• CN Tower
• Toronto Zoo
• Pearson airport
• University
• Hospital
• Bus stop
• Bridge
• 2 storey building
• Church
• Park
• River
• Street car
• Restaurant
• Ambulance
• School bus
• Casino
• Gym
• Library
• Police car
• Airplane
• Ship
• Town houses
• School bus
• Condo building

5. PI Planning – Program Backlog & Planning

6. ALL TEAMS INTEGRATE FEATURES AFTER
EACH SPRINT
SPRINT 1 SPRINT 2

7. SPRINT 3 SPRINT 4

8. Reflect
• How did you feel being part of a bigger team?
• How would you compare what you planned to what you completed?
• How was integration at the end of every sprint? Given what you now
know, would you have planned differently?
• How does Business Value relate to Story Points?
• Did you always agree with the Product Owner’s Business Value
scoring?
• What did you learn?