Presented at Agile Portugal.
http://www.agilept.org/program/talk-tiago-andrade-e-silva-2
XP Game is a way to go from theory to practice by simulating a real project managed with Agile concerns in mind. It enables a quick and fun way to understand concepts like velocity, story estimation and team motivation amongst others. There are no special requirements to attend this session and play the game. The goal is for each team to produce as much “work” and deliver as much business value as possible during the allotted time and iterations. This first session will introduce the concepts and explain the game to be played on the second session.
6. Tiago Andrade e Silva
• CTO @ Fullsix Portugal / Backlog
• Maste in Eng. Informática (pré bolonha)
• Post. Grad. in Gestão de Empresas Tecnológicas
• Scrum Trainer
12. Story Points
“Story Points are units of relative size used in estimating
software requirements as an alternative to units of time”
Wikipedia
@ Tiago Andrade e Silva
13. Story Points
“How long ?”
Vs
“How Big ?”
@ Tiago Andrade e Silva
17. XP Game
The game simulates:
• Estimating user stories
• Planning sprints
• Implementing stories
• Restrospective
• Measure velocity
• Teamwork
• Motivation
• Competition
• …
@ Tiago Andrade e Silva
18. XP Game- Sprints
• Each sprint:
• Customer delivers new stories
• Developers estimate stories
• Client team (the same) gives priorities (plan)
• Dev Team implements and Coach Validates
• Retrospective
• Game: 3 sprints
@ Tiago Andrade e Silva
19. XP Game
• Played in teams:
• 4 to 6 members per team
• Team will have Dev and client roles
• Goal: Maximize delivered Business Value
• Team with highest Business Value delivered wins.
• Bonus for ending early: 500 points.
@ Tiago Andrade e Silva
20. XPGame
• Each sprint: “3 minutes”
• Only counts “working time”
• Bonus and penalties (+ 50%, - 50%)
@ Tiago Andrade e Silva
21. XPGame - Coach
• Prepares User Stories to be implemented
• Validates work
• Controls Time
• Cannot execute
• Can help in estimation and planning
@ Tiago Andrade e Silva
23. PLAYING:
• Sprint
• Estimate (Team assumes dev role)
• Plan (Team assumes client role)
• Implement (Team assumes dev role)
• No multitasking – one story at a time.
@ Tiago Andrade e Silva