Scrum Game


Published on

Our version of the classic Lego 4 Scrum game

1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Scrum Game

  1. 1. Scrum Game
  2. 2. Learning the principles of the Agile manifesto1. OPEN BACKLOGS THAT TRIGGER IDEATING over DETAILED INSTRUCTIONS TO FOLLOW Invitation for collaboration between a customer and teams2. MINDFUL PRODUCT DEVELOPMENT over A SERIES OF TASKS TO ACCOMPLISH Teach product development, not micromanagement on a task level3. TEAMS COLLABORATING TOWARD COMMON SUCCESS over COMPETITION FOR SCORE A chance to practice skills of inter-team collaboration4. USEFUL METRICS TO ASSESS BENEFITS OF AGILE over FIGURES THE TRAINERS ASKED TO COLLECT teach the team to own their process2
  3. 3. Organization• Teams of 4 to 8• Timing: ~100 minutes• Boxes of bricks: lego, kapla,…• Board, markers, flipboard sheets of paper,sticky-notes• Big table: ideally one per team3
  4. 4. Roles• Product Owner: this is me. I represent theclient.• Team members: all of you.• Scrum master: optional. The game can beplayed without scrum master. This is up toyou: self–organize.4
  5. 5. PRE-GAME: Organizing Teams (5 min)• Self-organize yourself in groups of 4-8 peopleand allocate the working space and material5
  6. 6. PRE-GAME: Project Chartering (5 min)• All teams are building a singleproduct for the same vendor,represented by the ProductOwner.• The product is a CITY.• Building blocks are lego / kaplabricks.• I am the main decision maker ofthe product – it is my city.• I will be involved in thedevelopment process by beingavailable to answer questionsand provide feedback.6
  7. 7. PRE-GAME: Building the Backlog (15 min)• We want to build:– Small house: one storey building (several)– Big house: two storey building (several)– Shop– School– Church– Hospital– Kindergarten– Bus stop– Intersection (can be drawn)– Park (can be drawn)– River (can be drawn)– Bridge7
  8. 8. PRE-GAME: Estimating (15 min)• Choose an estimation method, but keep itsimple and keep it fast.– Recently, agile gurus have recommended droppingestimates.• A possible approach is t-shirt sizing: S, M, L, XL• Or you may use story points: 1 2 3 5 8 13• Or planning poker8
  9. 9. GAME: Sprint Planning (10 min + 3 min)• Build a unique Planning board for allteams to make sprint planning morevisible:– 3 sprint zones for each team– Release Burndown chart• You have 3 minutes to plan sprint #1• Sprint duration: 7 min9
  10. 10. GAME: Sprinting (7 min / sprint)• 7min ticking…• Start building10
  11. 11. GAME: Reviewing (5 min)• Stop building• Demo: where is the demo of my city?• Update planning wall• Update Release Burndown chart• Retrospective: “how can we make it better the nextsprint?”11
  12. 12. GAME: release cycle• Loop on sprints #2 and #312
  13. 13. POST-GAME: Debriefing• How did it feel being on a Scrum team?• How did the short iterations go?• How accurate were the estimations?• What would we have done differently from the beginning, if we had another chance to play thegame?• What was the job of the Product Owner?• How did it feel after the first sprint when most items required re-work?• How will your strategy change, if you know the Product Owner is unavailable during sprints?• How did inter-team communication go? Were there any dependencies? How were they resolved?• What did you learn?13
  14. 14. Thank you for playing14
  15. 15. References:• www.lego4scrum.com15
  16. 16. Preparation for this workshop• Gather material:– Flipboard pages– Markers of different colours– Sticky notes– Whiteboard– For each team, 1 set of lego/kapla• Prepare sticky notes with buildings16