Tech Debt Stories
Technical Debt Stories is an attempt to solve the Technical Debt problem by creating fake User Stories. Since User Stories are about delivering real business value to the customer, I don’t recommend inventing these. Further since the Product Owner prioritizes the Product Backlog in Scrum, it would seem nothing technical belongs there.
Many teams maintain their own list of technical debt and pull from it using their own criteria. Sometimes, the best reason, we’re already working in an area of the code base that is debt-ridden. Work on debt from that area.
- Technical User Stories or The Team Try to Pull a Fast One on the Product Owner
- Scrum by Example – How to Deal with Bad User Stories as a ScrumMaster
- Scrum by Example – Stop Digging New Holes
- Technical Debt a Perspective for Managers
- Scrum Anti-Patterns: The Hardening Sprint - Hint: they contribute to the problem
Resource Links
- As a Developer is not a Story — Bill Wake
- Technical Stories: We don’t need ‘em — Ron Jeffries
- Refactoring not in the Backlog- also Ron Jeffries
- Technical User Stories” Ariel Valentin