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?
5527
-
Just ask!
May 20, 2013 - No Comments
-
Musings over lunch
April 26, 2013 - 4 Comments
-
Fun with Easter Eggs
March 9, 2013 - No Comments
-
Lean Coffees in England!
March 7, 2013 - No Comments
agile
Agile 2009
Agile Coach Camp
agile coaching
agile development
agile teams
agile testing
agile testing book
agile testing days
agile testing training
article
articles
ATDD
awta
Belgium Testing Days
big agile
book review
books
brainstorming
collaboration
communication
conferences
customers
donkeys
estimating
experiments
frameworks
interview
learning
learning for testers
planning
quality
retrospectives
Software Testing Club
stareast
technical debt
test automation
testers
test frameworks
testing
test tools
training
whole team approach
writing
writing about testing
Recent Tweets
Categories
agile teams
agile testing
agile testing quadrants
agile testing training
big agile
book review
communicating
conferences
continuous integration
diversity
documentation
donkeys
estimating meetings
experiments
exploratory testing
feedback
fun
Functional test tools
hiring
interview
Lean Coffee
learning for testers
magnificence
mind maps
pairing
planning
podcasts
Publications
remote team members
requirements
Retrospectives
Selling Agile
shortened feedback loop
software quality
Stickyminds Blog
TechTarget articles
Techwell Blog
test automation
training
Transitioning to agile
Uncategorized
webinar
weekend testers
Whole Team Approach
writing
© 2013 Agile Testing with Lisa Crispin | Providing Practical Agile Testing Guidance



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!