SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Successfully reported this slideshow.
Activate your 14 day free trial to unlock unlimited reading.
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