Successfully reported this slideshow.

Agile Bug Fixing (Zero Bug Policy)

1

Share

Loading in …3
×
1 of 15
1 of 15

More Related Content

Related Books

Free with a 14 day trial from Scribd

See all

Related Audiobooks

Free with a 14 day trial from Scribd

See all

Agile Bug Fixing (Zero Bug Policy)

  1. 1. The Art of Agile Development: No Bugs Daniel Dominguez 1
  2. 2. Rather than fixing bugs, agile methods strive to prevent them. 2
  3. 3. Methods for triaging bugs 1 2 3 4 3
  4. 4. 1. In the Product Backlog 4
  5. 5. 2. In a Hardending Sprint 5
  6. 6. 3. Bug Court 6
  7. 7. 4. Dedicated Sprints 7
  8. 8. How are we? 8
  9. 9. Our Bug Metrics May 2016 9
  10. 10. May 2016 (18 Bugs Open) 10
  11. 11. May 2016 (18 Bugs Open) 11
  12. 12. zero bug policy What if? 12
  13. 13. 13
  14. 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. 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

×