Configuration Management
Issue Tracking
Issue Reports
|
Priority
Definition:
- Priority is the chief factor determining the order in which developers work on a task.
- It is not a judgment of importance to the customer.
- In theory, all priority 1’s within a target release should be addressed before priority
2’s, and so on.
- Therefore, it is the Product Manager who sets this field.
- Thou Shalt Not Ship with known Priority
1 Bugs.
|
Priority 0 - Needs Triage
- This issue has not yet been reviewed by a product manager to determine its
priority.
Priority 1
- This issue must be fixed prior to release.
- If there is any chance that we would ship with this bug, then it is NOT
a priority-1 issue (by definition).
- Issues can be re-prioritized by product managers if we determine that time
constraints would preclude fixing this prior to release.
Priority 2 - 4
- All other priorities simply indicate what order in which to address
issues.
- The product manager has the final say on what priority an issue gets assigned,
because priority determines how developers spend their time.
Priority 5
- Priority 5 issues are still legitimate issues, but chances are slim to
none that we will actually address them. More often than not, these issues get rolled over to the next release after the product ships and a full-scale review of issue-based workload is performed.
Contact Primary Goals for a detailed review of your issue tracking system, or for consultative assistance to ensure that you have a smooth deployment of your CM system.
|
