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?
The Agile Testing Days program always includes a vast range of topics. Some are perennial favorites, some are totally original. This second post about stuff
ATD 2023 – I don’t have enough words to describe the joy, the human connections, the learning. I think I do have words to share
Leading quality in software organizations – what is the best way? For more than two decades now, software organizations have wondered: when we transform to
Recently, Melissa Fisher asked a Slack community I’m in for ideas on creating successful workshops. Community members who are highly experienced in delivering excellent training
In our new Agile Testing Fellowship Donkeys & Dragons video chat episode, Janet Gregory switched from being co-host with me, to being a guest with
A conference called Agile on the Beach sounds like a summer vacation! By scheduling some free time before and after the conference, I did turn
4 comments on “Technical Debt Sprints”
Hi Lisa,
Did you see this old article of me?
http://www.hanoulle.be/2010/04/cleaning-a-kitchen-a-good-metaphor-for-refactoring/
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!