agile bug fixing (zero bug policy)

15
The Art of Agile Development: No Bugs Daniel Dominguez 1

Upload: daniel-dominguez

Post on 15-Feb-2017

292 views

Category:

Software


9 download

TRANSCRIPT

Page 1: Agile Bug Fixing (Zero Bug Policy)

The Art of Agile Development: No Bugs

Daniel Dominguez

1

Page 2: Agile Bug Fixing (Zero Bug Policy)

Rather than fixing bugs, agile methods strive to prevent

them.

2

Page 3: Agile Bug Fixing (Zero Bug Policy)

Methods for triaging bugs

1 2 3 4

3

Page 4: Agile Bug Fixing (Zero Bug Policy)

1. In the Product Backlog

4

Page 5: Agile Bug Fixing (Zero Bug Policy)

2. In a Hardending Sprint

5

Page 6: Agile Bug Fixing (Zero Bug Policy)

3. Bug Court

6

Page 7: Agile Bug Fixing (Zero Bug Policy)

4. Dedicated Sprints

7

Page 8: Agile Bug Fixing (Zero Bug Policy)

How are we?

8

Page 9: Agile Bug Fixing (Zero Bug Policy)

Our Bug Metrics May 2016

9

Page 10: Agile Bug Fixing (Zero Bug Policy)

May 2016 (18 Bugs Open)

10

Page 11: Agile Bug Fixing (Zero Bug Policy)

May 2016 (18 Bugs Open)

11

Page 12: Agile Bug Fixing (Zero Bug Policy)

zero bug policyWhat if?

12

Page 13: Agile Bug Fixing (Zero Bug Policy)

13

Page 14: Agile Bug Fixing (Zero Bug Policy)

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

Page 15: Agile Bug Fixing (Zero Bug Policy)

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