The document provides guidance on prioritizing a product feature backlog by scoring features based on three criteria: demand, difficulty, and impact. Demand refers to how much users want the feature. Difficulty considers how challenging it will be to implement. Impact evaluates the effect of the feature. Features are scored 1 to 3 on each criteria and totaled, with higher scoring features developed first to manage demands while considering effort and effects. The approach aims to help organizations tackle feature requests and determine the best next steps.

1. What the f*$k should
I build next?
Managing a feature back log
Carlos Saba
@kungfucarlos

2. Death by feature requests!

3. Designer

4. Developer

5. Where to start?

7. Demand

8. Demand
Difficulty

9. Demand
Difficulty
Impact

10. Demand
Everyone is asking for it Score: 3
People like the idea Score: 2
No one give a sh!t Score: 1
Why?

11. Difficulty
Brain surgery is easier Score: 1
Can take it in my stride Score: 2
Why?
Done it! Next? Score: 3

12. Impact
World changing Score: 3
Might raise an eyebrow or two Score: 2
Tumble weed Score: 1
Why?

13. Demand +
Difficulty +
Impact
= Backlog busting score!
Features that get big scores get built first

14. Start building sh!t

15. Thank you!
Carlos Saba
@kungfucarlos