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…

Dice Of DebtDados da dívidaDados de la deudaDice Of DebtDés de la dette

This game illustrates the importance of dealing with technical debt. Over the course of 10 sprints, a software development team will try to deliver as much software value as possible. The team can invest in measures that reduce the burden of technical debt. While there’s a short-term price, these measures also bring long-term benefits. Before you begin, download the ZIP file containing all the materials…

The Scrum Gauntlet of Debt

 Overview: A quick and easy demonstration/game to illustrate why an agile team needs to do refactoring and the related XP Practices in addition to Scrum. It never fails to create the A-HA moment for a team and team management as to why, when and how to do refactoring.    Learning Points: Scrum without XP will lead to technical debt and ultimately a legacy system.  …

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…