Timeline for With Scrum, how do you keep from dropping the little things?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 16, 2012 at 9:20 | comment | added | Ben K | @Zsolt - On my current project I raised the issue right at the beginning. I explained how Tech Debt can snowball into a maintenance nightmare or even derail a project that everyone thought was going well. Since Agile is focused delivering quality, and the team is empowered to achieve this, I haven't had too much pushback on it yet. Obviously there is a balance to be made. If you try to tackle too much Tech Debt in one sprint the PO will feel that nothing tangible is getting done. For particularly large T.D. I work with the PO to try and incorporate it into proper Stories, if possible. | |
| Feb 15, 2012 at 15:34 | comment | added | Zsolt | Just out of curiosity, how did you convince your product owner to let you work on collected technical debt rather than user stories? Ours always forbade us to work on them. He wasn't right, but I'd like to know how to approach a PO with an issue like this. | |
| Feb 15, 2012 at 9:38 | history | edited | Ben K | CC BY-SA 3.0 |
Fixed grammar
|
| Feb 14, 2012 at 16:53 | history | answered | Ben K | CC BY-SA 3.0 |