3 ms·
We tend to bundle that work up and include it in tickets with the full acknowledgement of the rest of the team. "Oh, since we're adding new email features, we'
by matthewmacleod 10y ago
We tend to bundle that work up and include it in tickets with the full acknowledgement of the rest of the team.
"Oh, since we're adding new email features, we'll need to clean up some of the old email code. That will add additional complexity to this task, so we will estimate it higher."
It works, allows us to still track the impact on velocity, keeps everyone informed, and makes technical debt clear and trackable.
- xwkd 10y agoI believe this is the correct approach. You're not hiding the complexity of the work, and you're also not compromising on quality. This leaves only the task of saying "no" when asked if you, "for now, could just..."
- maxxxxx 10y agoThis is how it should work in my view. You just need managers that are disciplined and don't tell you to not clean up old code because of deadline pressure.
- abritinthebay 10y agoThis is exactly what is supposed to happen in a Scrum system. If someone is not doing this they're not doing Scrum - just something they called Scrum to pacify people