It’s difficult to teach the principles of Lean and Agile simply by lecturing. People need to experience the principles by themselves to get a feeling for how it all works. By playing a game, you can gain experience without messing up your daily work or getting engrossed in the technical details. This is why games and simulations are used to help people learn and evolve in a better direction.

With the Kanban Pizza Game 2015, participants can discover what Kanban feels like. While other Kanban games are usually focusing only on the mechanics of the board and on the flow in an existing Kanban system, the Kanban Pizza Game (initially developed by Agile 42) teaches you how to get from an existing process to a Kanban system.

The Kanban Pizza Game by agile42 is licensed under the Creative Commons Attribution-Share Alike 3.0 License.

 

 
 

Outline/Structure of the Workshop

Narrative courtesy of Agile 42:

The Kanban Pizza Game was initially developed by Agile 42: http://www.agile42.com/en/training/kanban-pizza-game/ detailing valuable learning objectives for participants:

  • Experience how a Kanban system emerges from an existing process (like we do it in the real world)
  • Experience a whole Kanban system (as opposed to focusing only on the Kanban board and related mechanics)
  • Understand that boards are context-dependent: for any given process there are many different board designs that are adequate and useful, but not necessarily one single optimal board
  • Understand the effects of limiting your Work in Progress
  • Experience self-organization and adaptation
  • Have fun!

My enhanced 2015 version introduces additional features to the game that reflect real-life impacts to individual and team performance.  The new features include:

  • Incentives
  • Scope change
  • Capacity variability

Learning Outcome

Participants gained a powerful insight and hands-on learning of:

  • The core Kanban principles
  • Transparency
  • Workflow visualization
  • Value stream
  • Prioritization / impact
  • Requirements
  • Scope change
  • Waste
  • Throughput
  • Flow theory
  • Measurements
  • Cycle time
  • Batch sizes
  • Queues
  • Blocked items
  • Bottlenecks
  • Systems thinking
  • Kaizen/continuous improvement

I have been running this workshop for teams all over the world and have introduced as a core module to the Product Owner training that I deliver.  

The workshop is an excellent training and coaching opportunity for anyone involved in producing a product.

Target Audience

Anyone involved in the development lifecycle or production of a product

schedule Submitted 5 years ago

Public Feedback


    • Liked Yuval Yeret
      keyboard_arrow_down

      Yuval Yeret - Understanding and Implementing DevOps Flow

      480 Mins
      Workshop
      Intermediate

      DevOps seeks to extend the agile benefits of Flow, Collaboration, Inspect and Adapt thinking all the way to Production. While DevOps and Continuous Delivery were born in the world of web operations in companies like Etsy, Google, Amazon, Facebook and Flickr (also called Unicorns in the DevOps community) it is now clear that Enterprise IT/Product Development companies (also known as Horses) can  also benefit immensely from the ideas and practices and achieve similar results if they manage the change/journey towards DevOps in a way that makes sense in their context. In this workshop we will introduce the concepts of DevOps and Continuous Delivery and help attendees figure out how DevOps can fit into their world as well as how a “DevOps Implementation” might look like.

    • Liked vinaya muralidharan
      keyboard_arrow_down

      vinaya muralidharan / Sutap - The Snowball Effect - From Team Kanban to Enterprise Kanban

      20 Mins
      Experience Report
      Intermediate

      About two years ago, we embarked on our journey towards Agility and Kanban was our vehicle.

      But Kanban had people worried.

      How can we not have detailed plans?! How can we limit WIP when we have so many things to work on?!

      We have due dates to meet! And so on.

      We would like to share one of the approaches that we adopted to help move the change along.

      In addition to focusing on the Kanban implementation at the project levels, we adopted another route – to work through the individuals and the teams – a grounds up approach. We encouraged people and teams to use Kanban boards to manage their daily tasks.

      You have difficulty in managing personal stuff? We’ll help you manage better!

      You have issues in managing team level priority? Look what we did within our team- we have a Team Kanban and we are now much better organized!

      One by one we saw people getting interested. The movement gathered steam - we worked directly with a handful of people and they in turn got their peers onboard. And we saw various flavors like Personal Kanban, Team Kanban cropping up all over the place – even in our Travel Office and Corporate Office. What this did was give people a safe, controlled environment to experiment and learn in.

      As they got used to the ideas of limiting WIP, pulling work, visualizing work and “stop starting, start finishing”, it gave them the confidence to work this way at the project level too. And it made our lives as change agents just a wee-bit easier!

      We welcome you to come hear our story about nurturing the change towards Agility by making it a grass roots movement.

      A brief introduction to Amdocs - Amdocs is a leading provider of Customer Experience systems and services in the telecommunications domain, typically doing large scale transformation projects.

    • Liked Debbie Wren
      keyboard_arrow_down

      Debbie Wren / Asheesh Mehdiratta - Growing up the Product Management Tree House

      45 Mins
      Case Study
      Beginner

      Product Management for agile projects is still in the 1970’s era or is it really?

      Organizations today face tough challenges in overall agile delivery, with the product management teams still catching up and coming to terms with the new agile beast, which churns out functionality every 2 weeks. The product managers do not have a clue as to what exactly they need to do next with these 2 week deliverables! OK at least some do have an idea, but most product management teams struggle to keep pace both with their internal product owner needs on one end and the external customer /market facing demands on the other.

      This talk focuses on our experiences of building product management capabilities at large scale, to overcome these challenges, and provide some insight with practical tips implemented. Join this session to learn from our experience and grow your own product management tree house.