Posted in Scrum Add-ons

Prioritising Problems

Guidance on Prioritising Problems

By Risk (1, pg 45)

  • Highest risk: value ratio gets top priority
  • Work on the riskiest ones first
  • Keep all on a the backlog 

Prioritisation Techniques

Importance vs Satisfaction Framework (2, pg 47)

This technique is used for evaluating potential product opportunities

Importance vs Satisfaction (2, pg 47)
  • Competitive example is Excel. High important to users and it is the leading example. So product in this space to compete needs to be something like the online sheet tools for collaboration
  • Opportunity example is Uber where user satisfaction was low with taxi service but their need for a solution is very important to them
Measuring Customer Value
  • When importance and satisfaction are both percentages:
Customer value delivered = importance x satisfaction

Opportunity to add value = importance x (1-satisfaction)
Customer Value Example
  • For orange it is:
    • Customer value delivered: 0.9 x (0.35-0.2) = 0.135 
  • For blue it is:
    • Customer value delivered: 0.6 x (0.9-0.6) = 0.18 
  • So blue created marginally more value than orange. 

The Kano Model (2, pg 64)

  • Performance needs – adding more will increase satisfaction. For example fuel efficiency on a car. Increasing this will always increase satisfaction.
  • Must-Have needs – they never increase satisfaction. They only decrease it if they are missing 
  • Delighter needs – the customer is not dissatisfied at all if they are missing as they are unexpected and result in very high satisfaction if they are included
Using the kano model to compare with competitors
FeatureCompetitor ACompetitor BYour Product
Must Have Feature 1Yes/ NoYes/ NoYes/ No
Must Have Feature 2Yes/ NoYes/ NoYes/ No
Must Have Feature 3Yes/ NoYes/ NoYes/ No
Performance Feature 1High/ Med/ LowHigh/ Med/ LowHigh/ Med/ Low
Performance Feature 2High/ Med/ LowHigh/ Med/ LowHigh/ Med/ Low
Performance Feature 3High/ Med/ LowHigh/ Med/ LowHigh/ Med/ Low
Delighter Feature 1Yes/ NoYes/ NoYes/ No
Delighter Feature 2Yes/ NoYes/ NoYes/ No
Kano Table

Return on Investment

Approximating ROI (2, pg 84)

References

  1. Lean UX by Jeff Gothelf
  2. Lean Product Playbook by Dan Olsen

One thought on “Prioritising Problems

  1. Pingback: Product Backlog

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s