October 2013
Intermediate to advanced
224 pages
7h 58m
English
Software projects and teams that have been in place for some time have likely accumulated waste that they need to address. One of the reasons that waste does hang around is that removing it is hard to prioritize over adding new features that customers request, as well as other business priorities. And yes, there are scenarios in which it does not make business sense to remove waste. But a choice should be made instead of just letting it continue to hang around.
To evaluate whether it makes sense to remove the waste, track the debt in the backlog as a user story that defines the value of solving the problem. For instance, refactoring some part of the code may reduce customer incidents by 25 percent. Or perhaps ...
Read now
Unlock full access