Simple Schemes
A basic prioritization method that tags work with simple ranks like 1, 2, 3 or labels such as High, Medium, and Low. It is easy to apply but often leads to priority inflation, where too many items are marked as Priority 1 or High.
Key Points
- Uses coarse categories (numbers or High/Medium/Low) to order work quickly.
- Common pitfall: most items get labeled Priority 1 or High, reducing usefulness.
- Lack of clear criteria makes categories subjective and inconsistent.
- Mitigate by defining entry criteria, capping the High category, and applying relative ranking when needed.
Example
During backlog refinement, a team labels items as High, Medium, or Low. After a few sprints, 70% are High, so the order of work is unclear. The project manager sets objective criteria for each level and limits High to 10 items. Anything beyond the cap must be downgraded or split, restoring clarity.
PMP Example Question
A team uses priorities 1, 2, and 3, but 80% of the backlog is marked as 1. What should the project manager do first?
- Replace the scheme with a complex weighted scoring model immediately.
- Define objective criteria for each level and limit how many items can be labeled 1.
- Allow stakeholders to keep marking critical items as 1 to avoid conflict.
- Sort the backlog alphabetically to break ties among Priority 1 items.
Correct Answer: B — Define criteria and cap the top category
Explanation: Establishing clear entry criteria and a cap curbs priority inflation while preserving a simple scheme; more complex methods can be considered later if needed.
