the ball point game

Introducing agile by the Ball Point Game

Suppose on one day you need to introduce a new team to the agile mindset and suppose managers will participate too. Do not start it by giving a standard presentation with slides about agile values and principles, self-organizing teams and so on, use a game instead! More precisely, use a physical agile game: the Ball Point Game (invented by Boris Gloger).

The game simulates an agile production process, it is basically an analogue of the Scrum process. The team will self-organize and form a process based on the rules provided. The objective is to pass as many balls as possible in the given timeboxes through the team by following certain rules.

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 a large number of brightly colored ping pong balls (about 60 for a group of 50 people) and you may want a whiteboard to do the debriefing and a stopwatch.

The Rules
The rules are quite simple and the more people you have, the more exciting it can be. You play the game best with more than 6 participants and it would be an excellent game for larger groups up to 50 people.
- You are one big team.
- Each ball must be touched at least once by every team member.
- Each ball must have air-time, in other words, it must not be passed directly from hand to hand.
- You cannot pass the ball to the person immediately to your left or right.
- Each ball must return to the same person who introduced it into the system. For each ball that does, the team scores 1 point.
- If you drop a ball, you cannot pick it up.
- There will be a penalty (points deducted) if you break any of the rules.
- If you’ve played this game before, please participate silently so you don’t spoil it for others.

Game play
In the game, there are two roles, only: the team (included PO) and the facilitator.
Here’s how to play the game:
- Allow the team to prepare and to determine how they will organize themselves. (2 min)
- Ask the team for an estimate how many balls they can pass through the system at the first run (each run is 2 minutes).
- Run the first iteration. (2 min) – at the end check if someone counted the balls
- Allow the team to discuss how to improve the process. (1 min)
- Repeat for five iterations (recording the estimate, actual and changes each time).

Hints for the facilitator
Try not to make the hints too obvious too early in the game. For instance, after a couple of iterations, during the learning minute, you might want to give the team clues, such as eliminate waste, maximize resources. Later you might want to hint that they should use both hands, and later still that they could cup heir hands together to drop fewer balls (less waste).

Conclusion
At the end of the exercise, debrief for five to ten minutes. There are a number of basic agile principles and values that are worth talking about.
- Trust. See how to build trust in the team and in individuals.
- Self-organisation. See how the team makes decisions to work best, without control from outside managers.
- Inspect & Adapt. See how the team steps back and reflects in retrospectives on a regular basis to improve the own work.
- Timeboxed, incremental delivery. See how the team estimates, plans, and improves quality in an iterative manner.
- Agile ceremonies. Getting acquaintance with "Sprint", "Retrospective", "Planning", "Estimation".
- Learning. See how fast the team succeeds.

All in all, the Ball Point Game is a great ice-breaker, good fun and very thought-provoking.

Source:
Agile Games – ball point game