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…

Sustaining Agility

Learning Objective: Participants experience the attraction of short-term thinking and feel the long-term consequences. When to use this game: Play this game to understand the importance of investment in sustainable development practices. Time: 90-110 minutes Description: Have you been on a software project where each release gets harder and harder? Many projects fall into the tarpit of the Design Dead Core. Why do nearly all software…