Technical Debt Game – for non-technical people

Experience the difference between doing continuous refactoring … or not A game for groups from 3 to 5 people. Setup: 5 minIntroduction: 5 minTwo rounds of each 5-10 min so approx. 10-20 minDebrief: 5-15 min Purpose of the game: Explain and experience the effects and consequences of adding feature after feature and cummulating technical debt or doing and investing in continuous refactoring. Background: A team…

Kitchen PrioritizationKitchen Prioritization

The goal of this game is to understand how important it is to have choice criterias during prioritization and make them explicit. This game will talk about relative prioritization, implicit criterias, personal criterias, implicit expectations Le but de ce jeu est de démontrer à quel point il est important d’avoir des critères de choix durant une phase de priorisation et de les rendre explicites. Ce…

“Hitting the Target” — Business Value in Mission-Focused Organizations

How should organizations prioritize work in the face of conflicting goals and metrics? Help more people? Minimize delays? Prosecute more crimes? Lower costs? In this game participants will experience a dice-based simulation that has been created to explore these questions by examining the impact of these decisions on the performance of organizations in changing environments.

Weekend Escape an agile backlog management game

Timing:  20 minutes to prepare plus 30 minutes for Standard version, or 75 to 90 minutes for Extended Version Overview: Small teams collaborate to order a backlog with a specific business goal in mind. Once the team has produced their backlog, they review the output of another team and discuss the differences. Everyone participates and discussion plays a key part in the game. Participant’s eyes…

MyToy : An Agile Product Development Game

Timing: 2 to 3 hours Overview: An Agile product development simulation game with LEGO®, Scrum, story maps, experiments, etc. This game tries to cover an entire product development process, the Agile way, and is designed for a single team of 4 to 6 people. The team will build a story map and decide on experiments to make at each sprint in order to build the most suitable…