Agile Bug Fixing (Zero Bug Policy)
1 like1,718 views
The document discusses methods for preventing and triaging bugs in agile development, including placing bugs in the product backlog, fixing them in hardening sprints, using bug courts, and dedicating sprints to bugs. It also discusses metrics for tracking open bugs and implementing a zero bug policy by either fixing bugs immediately or closing them as "won't fix". The conclusions emphasize that bug fixing should be part of the engineering culture and that teams need balance between fixing bugs and sprint development.
Agile Bug Fixing (Zero Bug Policy)
- 1. The Art of Agile Development: No Bugs Daniel Dominguez 1
- 2. Rather than fixing bugs, agile methods strive to prevent them. 2
- 3. Methods for triaging bugs 1 2 3 4 3
- 4. 1. In the Product Backlog 4
- 5. 2. In a Hardending Sprint 5
- 9. Our Bug Metrics May 2016 9
- 10. May 2016 (18 Bugs Open) 10
- 11. May 2016 (18 Bugs Open) 11
- 12. zero bug policy What if? 12
- 13. 13
- 14. How does zero bug policy works? Bugs can be generalized into 2 categories: 1. Bugs that were opened during the sprint for user stories (features you are now implementing) - Fix them right away, otherwise the story/feature is not really DONE. 2. All the other bugs (regression, customer bugs, etc.). Non-sprint bugs. - Either fix them right away (or in the next sprint). Or close them as "won't fix". 14
- 15. Conclusions - Bug fixing should be part of our “Engineering Culture”. - Solving Bugs shouldn’t be considered a “Punishment”. - The team should have a balance between bug fixing and sprint development. 15