Prioritisation of bugs
- Paul Seiler (Unlicensed)
Owned by Paul Seiler (Unlicensed)
We need an agreed definition or understanding on the priority of the bugs we find during testing. The following is my suggested approach, but I am open to feedback
| Rating | Action | Urgency |
|---|---|---|
Highest | Must be fixed | Within 24 hours (if at all possible), as it delays other testing |
| High | Must be fixed | Within one week (if at all possible), but before go-live |
| Medium | Must be fixed | Should be fixed before go live, but can be later so long as fixed in the project. Could allow for fixing in the next phase of the project. |
| Low | Should be fixed | Should be fixed in the project, but can be left for BAU to address later |
| Lowest | No action required | We can live with it as is, indefinitely |