Number |
Name |
Reasons for Selecting |
Expected Response |
1 |
Show Stopper |
The company cannot continue its main line of business until this defect is resolved. A significant financial loss is occurring. |
By selecting this priority youare requesting that support staff and developers put in overtime (not get any sleep, get divorced, etc) to resolve the defect. |
2 |
High |
Either the customer or client is suffering loss as a result of the defect, however the loss is low enough to be bared for a few days. |
A release of the product will be generated specifically for this defect, however staff overtime will not be used. |
3 |
Normal |
Defects that are a priority to the business but are not currently causing loss. |
Defects of this priority will be resolved in the next release and, if necessary, the release will be held up to include them. |
4 |
Low |
This is where you should stick font change requests and defects that are unlikely to be noticed by a user of the system. |
The development team will attempt to resolve these defects in thecoming release, however if the schedule slips the release will not be held up. |
5 |
Fix in next release |
For feature requests and large changes to the system that will need estimating and planning. |
A project manager will look at these and cost them for inclusion in a future release. |
6 |
Don't fix |
Defects raised for information purposes only. |
No action will be taken on these. |
7 |
Undecided |
Use this while seeking advice on which of the above to select. |
No action will be taken on these. |