Prioritizing Requirements

Determining Value

Return on Investment

Customer Research 

• In depth interviews
• Focus Groups
• Observations
• Innovation Games
• Usability
• Support Groups

Market Opportunity Scores

2x2 showing satisfaction on the y access and importance on the x axis.

Kano Model

Purley in the solutions phase.

Insert Kano Model Here

Buying Features

Buy a Features

• Create a list of features
• Play with 4 to 7 customers at a time
• Price some features so customers have to pool money

Spend $100 on R&D

• Create a list of features
• Ask a customers to allocate R&D budget with their list of features

Subjective Value Determination

What happens when you have not data.

• Set a vision for the product and place requirement in the context of that vision
• Establish criteria and Rank Requirements

Example Matrix

Available for download at the 280 group site here. A way to do subjective prioritization

Risk

Mitigating Risk

• Identify Project Risks
  • Technical risk market risk, regulatory risk, delay risk
  • Move forward 

Maximize Technical Involvement

Allows developers to help determine problems

Evolve Features over Time

Identify Lifecycle

• Proof of Concept
• MVP 
• MMP

Managing Cost

• High cost, low priority features should be left out or built in another way.

Impact of Time on Priority

Some great graphs I didn't get....

Risk, Return and Cost View

2x2 showing return on the Y axis and risk on the x axis.

Summary

• It's tough to do.