Scrum Trainers Gathering (2/4): The Ball Point Game

Update: part 1, part 2, part 3 and part 4.

In part 1 of my report on the Trainers Gathering I gave an gave a summary of the events that occurred. In this post I’d like to discuss one of the exercises that was discussed. Boris‘ Ball Point game is a fun and exciting way to explore process flow. The rules are quite simple and the more people you have, the more exiting it can be. We played with about 25 people, but it would be an excellent game for large groups up to approximately 50 people.

The objective of the Ball Point game is to get as many balls through the team as possible within two minutes. Each ball must be touched at least once by every team member and must end with the same person with whom it began. After two minutes the team is allowed an additional minute to discuss the process and how it could be improved. The game is played a total of five times.

Initially, we (the Scrum Trainers) had difficulty getting a single ball through the system, but, after adapting our process, the interactions became more predictable and we started to make visible progress. It took four cycles for us to reach a point where we were both productive and having fun.

The fifth (and final) iteration was a challenge Sprint. Boris’ challenged us to get as many balls through the system as possible. In order to fully optimize the process, we rearranged the team and gave it a try. The final number was suitably impressive, given that only 15 minutes before we had difficulty getting a single ball through the system.

This rearrangement of the system leads to one of the more interesting points that Boris makes when running the game. That is, all systems have a natural velocity and if we want to increase this natural velocity, we need to change the boundaries of the system.

Playing the Game
In order to play the Ball Point game, you’ll need a large open space with enough room for everyone to stand. You’ll also need about 20 brightly colored tennis balls and you may want a whiteboard to do the debriefing. We play the game in the following way:

  1. Provide an overview of the game and the rules.
    • Everyone is part of one big team.
    • Each ball must have air-time.
    • Each ball must be touched at least once by every team member.
    • Balls cannot be passed to your direct neighbour to your immediate left or right.
    • Each ball must return to the same person who introduced it into the system.
    • There are a total of five iterations.
  2. Allow the team two minutes of preparation time to determine how they will organize themselves.
  3. Get an estimate from the team of how many balls they can pass through the system.
  4. Run a two-minute iteration.
  5. Allow the team one minute to discuss how to improve the process.
  6. Repeat for five iterations. Make the fifth iteration a challenge. If you need to, make up some ridiculous statistic such as “The world record is 150 points. Can you beat that?”

At the conclusion of the exercise, debrief for five to ten minutes. There are a number of interesting points that are worth talking about. Firstly, it’s worth mentioning the Deming Cycle. Secondly, it’s worth pointing out that every system has a natural velocity. And finally, it’s worth discussing “flow” and the necessary criteria for it. Boris’ full documentation of the game can be found here (link).

Bookmark and Share

About these ads
Comments
17 Responses to “Scrum Trainers Gathering (2/4): The Ball Point Game”
  1. pkmk says:

    please be more specific about the rules.

    nowhere in the rules you require for each ball to be touched by everyone. without this requirement i see no challenge in the game.

    are there any rules how people should stand according to each other?

  2. Daniel says:

    Can you give a little more insight into how to play this game? Can you tell us if all the balls need to be introduced by the same person? Also, can the ball be passed to someone in front or behind or must there be someone in-between in any direction? An example of how the game was actually played would be helpful as well. I would like to try this our teams and need to be sure we are doing it well to make sure the lesson is learned correctly.

  3. Kane Mar says:

    The rules are deliberately kept simple. The idea is to let the team self-organize and to see what happens. If there were a list of specific rules that would inhibit the team from self organizing and would defeat the purpose of the exercise.

    I’d suggest trying the exercise and seeing what happens. The most important rule for this exercise is …. have fun! =)

  4. Tigran says:

    Just can be interesting.. the real game video

    Thanks,

  5. YvesHanoulle says:

    I created a google group for agile games.
    I hope you will join us.

Trackbacks
Check out what others are saying...
  1. [...] from the Trainers gathering. In part 1 I gave an overview of some of the topics discussed and in part 2 I presented Boris’ Ball Point game. In this post I’d like to discuss anther exercise [...]

  2. [...] the next few weeks I will write about three of these sessions including Boris’ Ball Point Game (part 2), Jens’ Written Specification exercise (part 3), and Lowell’s Affinity Estimating [...]

  3. [...] 21, 2008 by Kane Mar Update: part 1, part 2, part 3 and part [...]

  4. [...] suvokti iteracijų ir timeboxing svarbą. vienas iš variantų – kane mar aprašytas kamuoliukų žaidimas. bet reiktų rasti dar bent kelis, nes epic fail atveju nebus jokios alternatyvos ;]  [...]

  5. [...] Ball point game: After the game people will realize things about self-organizing but especially about pulling work [...]

  6. [...] Also other games played: ball point game, tangled mess, doggy planning were a success and you actually saw people changing, bonding during [...]

  7. [...] have attended the Scrum Master training will know what i am talking about see the rules to the game here, I think this was the highlight for the students, they really enjoyed it and the practical [...]

  8. [...] The ball-point game, hehe, what fun that was, and a first for us… they played the game before and brushed off my [...]

  9. [...] topic of mine and one that I’ve presented before. On this occassion I was able play the Ball Point game with 70 participants in two teams! It was crazy, chaotic [...]

  10. [...] a couple of links (Kane Mar) (Declan Whelan) if you’re not familiar with the game. In a nutshell it involves a group working [...]

  11. [...] about how to test your organization, he started by telling about his experience about playing the ballpoint exercise, which is a kind of scrum-simulation, where the team has to do an exercise, then do a [...]

  12. [...] topic of mine and one that I’ve presented before. On this occassion I was able play the Ball Point game with 70 participants in two teams! It was crazy, chaotic [...]



Follow

Get every new post delivered to your Inbox.

%d bloggers like this: