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…

Retrospective Sailing – being agile

Retrospective Sailing is one of the most popular games teams adopt to reflect and map their way forward easily, in a fun, tactile and visual way. It can be used for many purposes where you want to review what’s going well, what could go better, and ensure you are responding regularly to the changing seas and horizons your businesses and team face.

Pass on Perfection

Pass on Perfection is a game suitable for creating a Minimally Viable Product or anything else you need that is minimally viable. Several people have reported on using it for teaming agreements, definitions of done or ready, or actions to possibly obtain some form of improvement. It’s simple and fun and plays out a bit differently with groups and subjects. It’s a mash-up of Yes…

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…