4 comments on “Technical Debt Sprints

  1. Hi Yves, yes, I saw that back when you published it, I love that metaphor and I often give people the link to your post. We’ve always been keen on refactoring and managing our technical debt, but it’s good for us to have reminders to step up our game on it.

  2. Back in the day when I was at Microsoft on Windows, we used an approach called “Milestone 0”. The idea is similar, except that we dedicated an entire milestone (maybe up to 3 months) just to “cleaning house”: closing bugs that didn’t reproduce, automating tests we didn’t get around to automating, cleaning up the code. Basically it was all about technical debt. This has become a practice I recommend to every team I join after, and I’m glad to see an analog in the Agile world.

  3. Thanks, Mark, it’s interesting to know about other approaches. We get technical debt whether we’re waterfall, agile or something else!

Leave a Reply

Your email address will not be published. Required fields are marked *