Study guides / CAPM: Certified Associate in Project Management / Product roadmaps & prioritization
Product roadmaps & prioritization
CAPM: Certified Associate in Project Management · quick review
Planning the product's direction over time, linking releases to strategy, and deciding what to build first when everything seems important.
The rules
- A product roadmap shows the planned direction, themes and major releases over time, linked to strategy. It's a guide, not a fixed schedule.
- MoSCoW: must have, should have, could have, won't have (this time).
- Kano model: basic needs (expected; missing them causes dissatisfaction), performance needs (more is better), delighters (unexpected; create satisfaction).
- Other methods: weighted scoring, cost of delay, value vs. effort, and dependency ordering.
- The MVP tests the core value with the least effort; later releases add to it based on feedback.
Common traps
- A roadmap describes outcomes and themes; putting fixed dates on every feature turns it into a schedule.
- Delighters become basic needs over time as customers come to expect them.
How it's tested
Applying MoSCoW or Kano to described features, and reading what a roadmap should contain.
Practise it
The full lesson, worked examples and practice questions are in Tickmark, where every answer choice is explained.
Open the full lesson