How bug prioritization works in agile projects vs non agile
When reporting a defect, we are setting the priority and severity of the defect. How this works with agile development? Is there any specific way ?
How bug prioritization works in agile projects vs non agile.?
Is there any other way of measuring the priority of a bug in agile projects?
briley last edited by
A generic answer is: It's contextual; the team and stakeholders (which is who understand better the context) should work towards finding a good way - and periodically analysis its efficacy and improve on it.
However, I see three major approaches. E.g.:
1 - The team defines strict rules for labels:
- High: The user cannot use some feature
- Medium: The user can perform the actions using some workaround
Low: An error that basically does not affect usage (such as a small typo)
It can be agreed that all High will be tackle in-sprint and every X sprint there will be time for Medium and/or Low.
2 - Stakeholders review all bugs and decide which and when to tackle each bug.
3 - Zero Bug Policy:
A Zero Bug Policy is simple. All bugs take priority over all new feature development or improvements. That’s it. There is nothing more.
An important corollary of this approach is that there is no such thing as bug priority, critical bugs, or minor bugs. An issue is either a bug or it isn’t. And if it is a bug, you need to fix it before doing other work.