Backlog busting
6 likes2,280 views
The document provides guidance on prioritizing a product feature backlog by scoring features based on three criteria: demand, difficulty, and impact. Features are given a score from 1 to 3 for each criteria, with 3 being the highest. These scores are then combined to calculate an overall "backlog busting score" that determines the order features should be built, with higher scoring features prioritized first. The author encourages the reader to start building the highest scoring features.
Backlog busting
- 1. What the f*$k should I build next? Managing a feature back log Carlos Saba @kungfucarlos
- 2. Death by feature requests!
- 4. Designer
- 5. Developer
- 6. Demand
- 7. Demand Difficulty
- 8. Demand Difficulty Impact
- 9. Demand Everyone is asking for it Score: 3 People like the idea Score: 2 No one give a sh!t Score: 1 Why?
- 10. Difficulty Brain surgery is easier Score: 1 Can take it in my stride Score: 2 Why? Done it! Next? Score: 3
- 11. Impact World changing Score: 3 Might raise an eyebrow or two Score: 2 Tumble weed Score: 1 Why?
- 12. Demand + Difficulty + Impact = Backlog busting score! Features that get big scores get built first