Technical Debt is so important that we must manage it directly – its management won’t happen by accident or as a byproduct of development. Since Technical Debt can’t be seen except by looking at the code, its presence must be made visible to the outside somehow. To make it visible, we use the Cleanup Story for this. A Cleanup Story is a story that tells us where the mess is and what we have to do to clean it up.
Share →
Author
Rawsthorne & Shimp
Dan Rawsthorne and Doug Shimp have been helping Scrum teams for years. They attribute their success to the thousands of students and clients who have given them the opportunity to test their knowledge and theories in the crucible of reality.