Refactoring -- Not on the backlog!
Should we put refactoring "stories" on the backlog?
Jul 30, 2014
•
4 min read
4.50
(24)
Technical Debt
Velocity
Refactoring
Software Craftsmanship
Summary
As "Technical Debt" grows in a project, a question frequently comes up: should we put refactoring "stories" on the backlog, so they are treated as jobs-to-be-done in the next sprint? Should we have an entire session just for refactoring? In this timeless article Jon Jeffries shares his experience as to how to approach refactoring - specially as the codebase grows and starts to slow down the overall velocity of the team.
Suggested Resources
Always do Extra
5.00
(1)
Technical Debt
4.71
(17)
The Technical Debt Trap
4.52
(27)
What is open source?
4.08
(25)
Cumulative Flow Diagram
4.80
(10)