Debt Tower.
A technical debt game. You have 12 sprints. Ship fast and the floor goes up crooked. Do it right and it goes up solid. Seven crooked floors and the tower falls.
By Badii Boutar · Updated
- Sprint
- 01/12
- Users
- 0
- Speed 100%
- Crooked floors 0/7
> No events this sprint.
Your run
- users
- features shipped
- of your team's time went to interest. In a 2019 study, developers lost of their time to technical debt.
Your run Best run / ship fast · # do it right · ~ refactor
Your real codebase has crooked floors too. The 14-day Trial finds them and ranks them by what they cost you. 14 days, one time, $995.
How to play
What the tower shows.
Technical debt is the extra work you pay later for shortcuts taken now. The tower turns that into something you can see. Each sprint adds a floor, and its width is what the team shipped that sprint.
- Ship fast ships the most this sprint, but the floor goes up crooked. That is the shortcut.
- Do it right ships a bit less, and the floor is solid. It also fixes a little of the old debt.
- Refactor ships nothing this sprint, but straightens up to four crooked floors.
- Every crooked floor slows the team down, and the slowdown grows faster than the debt. That is the interest. You can see it as the tower gets thinner at the top.
- Every feature you ship brings users each sprint, so features shipped early are worth more.
- Events like an investor demo or a traffic spike show up a sprint ahead, so you can plan for them.
The best runs are not the ones with no debt. They take a shortcut when it pays, then clean it up before the interest grows. That is how debt works in real teams too.
The game's numbers are a model made to feel right, not data. The calculator below uses numbers from studies.
Your team
What debt costs you.
Most of the cost of technical debt is developer time. Put in your own numbers. The defaults are the worked example from the cost of technical debt.
Sources
- Besker, Martini and Bosch, Software developer productivity loss due to technical debt, Journal of Systems and Software 156, 2019
- Stripe, The Developer Coefficient, Sep 2018
- Tornhill and Borg, Code Red: The Business Impact of Code Quality, Mar 2022
The 23% and the survey figure are what developers report, not time measured with a clock. Your team can be quite different.
Start
Find the debt that slows your team down.
In 30 minutes we look at where things stand, what you need from a CTO right now, and which option fits. Either way, you leave with a clear next step.
Or email badii@badii.studio
How the call goes
- 01You tell me about the product, the team and the next 6 months.
- 02I ask about the code, the stack and what keeps breaking.
- 03We pick the option that fits, or agree that none does.
09:00 to 20:00 CET
Founding rate: the first 3 clients get 20% off, in return for a named testimonial and a case study. On a monthly plan, the 20% applies to the first month.