Timing: This game may take from 20 to 30 minutes
Materials: A multicolor light weight ball, 6 strong sticks or plastic pipes with 21 inches each stick/pipe length, space to walk around while playing
Invite at least 6 volunteers to play this game. We are going to experience various scenarios in this game to demonstrate the need and importance of “collective code ownership” concept.
The volunteers have to come close and hand over them the sticks/pipes. Tell them the ball is their code base. In each scenario they have to make sure to play the scenario without dropping the ball. If balls drops then 1 penalty point. If they complete each scenario without dropping the ball then they get a bonus point. At the end of the game their total score will confirm how they could manage their code.
We need to keep a fixed time period to complete all scenarios mentioned below). This is to make the activity timeboxed.
Team can move to next scenario only after the previous scenario is done successfully without dropping the ball.
Note: If you are playing this game with more than one team then keep a separate scoring board to track the time and final score of each team.
Scenario – 1: Your code increases over a period of time
Scenario – 2: Your code is not static, it changes all the time
Scenario – 3: One team member develops more stories (more code)
Scenario – 4: Change the roles
Scenario – 5: A very important story came up!
They should not use the free hands and they need to just rotate the ball using their sticks/pipes
Scenario – 6: Couple of members on vacation
The team understands the importance of following concepts: