Contents
How do you give priority to a bug?
So, how do we prioritize bugs?
- Step 1: Collect information (bugs & feature requests) We think that the more information we have, the less risky our decisions are.
- Step 2: Assign values to each bug & feature request.
- Step 3: Outcome driven innovation.
What is a P2 bug?
P2. Site that does not function in some non-trivial way. Site that has really bad cosmetic problems (e.g., content overlapping such that it’s very hard to read).
What does P0 P1 P2 mean?
P0 – Don’t release without. Priority over all. P1 – If we are running out of time, scrap these and call it in upcoming sprints. P2 – Can wait until all others are done, usually nice to haves.
What is P0 P1 P2?
P0: Outage. P1: Critical. P2: Default. P3: Nice-to-have.
Why is it hard to prioritize bug fixes?
Long before the world discovered agile, prioritizing bug fixes was a challenge in software development. But agile’s short iterations make it even harder for many teams to decide which bugs to fix and which to put off.
What’s the best way to prioritize defects?
Prioritizing Defects by Policy: A Better Approach. Rather than taking time to reflect on each new bug individually, establish defect policies that determine how quickly a bug should be fixed. One defect policy might be that any bug affecting all users in a dramatic way gets fixed immediately, meaning it interrupts work in the current sprint.
Which is more important a bug or a new feature?
A bug causing a dead footer link might not be as valuable as a bug affecting the user’s payment. Many teams already proceed with that step by asking “how important a bug fix or new features is”. Though I recommend going even further by making use of the framework of outcome driven innovation.
How to determine the importance of a bug?
One way to evaluate the importance of a bug fix or feature request is by looking at the value your implementation is causing. A bug causing a dead footer link might not be as valuable as a bug affecting the user’s payment. Many teams already proceed with that step by asking “how important a bug fix or new features is”.