My teammate Nanda Lankalapalli and I have an article in StickyMinds on how we use technical debt sprints to keep our technical debt to a manageable level. There are lots of approaches to managing technical debt – what works for your team?
My Agile Testing Days USA 2023 experiences, Part 1!
Agile Testing Days USA 2023 brought me lots of new learnings, new friends, new energy! I plan to share my experiences here over the next
4 comments on “Technical Debt Sprints”
Did you see this old article of me?
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.
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.
Thanks, Mark, it’s interesting to know about other approaches. We get technical debt whether we’re waterfall, agile or something else!