The lean/agile penny game has become a standard way to demonstrate the benefits of small batch sizes in a production flow. However, as a demonstration of the effects of agile transformation on a software development team it is woefully inadequate. In this article we describe the classic penny game as played in much agile training, critique its accuracy as a model for agile software development, and provide a simulation that you can run yourself, showing what will happen if the software developers are not supported in adopting the practices of Extreme Programming.
A series of blog posts.
The simulation below consists of three production lines or teams. Each team executes the same process in exactly the same way, but each has been configured with parameter values that represent different software development processes:
The configuration parameters are:
To run all simulations, press the play button below. You can pause at any time, or use the reset button to start again from an empty project. The "sliders" button displays the configuration parameters used for each team, and shows how these values have changed during the simulation run.
Please note that this simulation requires a good deal of computing power, so it may slow up after a couple of hundred ticks. Enjoy!