Models

Kanban Pizza Game

The Kanban Pizza Game offers a practical introduction to Kanban by allowing participants to engage with the methodology hands-on. Unlike many Kanban games that focus solely on board mechanics, this game emphasizes transitioning from an existing process to a Kanban system. It encourages teams to visualize their workflows and make modifications actively.

Game Structure

  • Theme: The game revolves around making paper pizzas, a universally understood task that diverts attention from IT-specific scenarios. Participants cut and assemble pizza slices according to a given recipe.

  • Objective: Participants learn how a Kanban system emerges from an existing workflow, the importance of limiting Work in Progress (WIP), and the benefits of self-organization.

Workshop Format

The Kanban Pizza Game is designed for a half-day workshop. Ideally, sessions should last around two hours, allowing time for reflection and discussion.

Learning Outcomes

Participants will:

  • Experience the evolution of a Kanban system from a real-world process.

  • Understand that boards can be context-dependent, with multiple valid designs for different processes.

  • Recognise the importance of limiting WIP to enhance flow and communication.

Gameplay Flow

  1. Initial Process Creation: Teams begin by constructing as many Hawaiian pizza slices as possible within a set time, using paper materials.

  2. Introduction to Kanban: Facilitators introduce Kanban principles, such as visualizing workflows and managing flow after the first round.

  3. Rounds of Play: The game consists of multiple rounds where teams refine systems, introduce customer orders, and handle complexities like new pizza recipes.

  4. Final Visualization: The last phase involves creating a real Kanban board that reflects the team's workflow and reinforces the learned principles.

The Kanban Pizza Game is not only a fun and interactive way to learn Kanban principles but also fosters a deeper understanding of how to implement Agile methodologies in real-world contexts.

References:

For more details, visit agile42.

Last updated