際際滷

際際滷Share a Scribd company logo
NIMBLE FRAMEWORK
FEATURE PRIORITISATION
PRACTICAL PRODUCT MANAGEMENT SERIES
MANOJ AGARWAL & TEAM
TOPICS
HOW TO DEFINE A PRODUCT
PRIORITISATION - To be or not to be
User Needs and wants and Struggles
Identify user needs - why do we need the product
VROOM - The art of sizing
Ask the question Why?
Ask the question Why 5 times
What is Product Management and what it is not
User centric product design
Data enabled product design
A/B testing and the 'C'
How to eat the elephant
Art of trialing a Product
MVP Demystified
External guest speakers - ad-hoc schedule
Define the product concept
The One Thing
Untangle the spaghetti
Creating a Product roadmap
How to write great user stories
MVP or PoC or Prototype - myths Demystified
How to measure and iterate and discard
Importance of Meaningful User Actions and how to capture them
How to run a successful design sprint
How UX Design integrates with Agile and Scrum
Demystified - if we build it they will come
Microservices as a Product
Product of products
NIMBLE FRAMEWORK 2
FEATURE PRIORITISATION
OBJECTIVE:
I WANT TO BE ABLE TO
PRIORITISE FEATURES OF MY PRODUCT
USING A SIMPLE METHOD
NIMBLE FRAMEWORK 3
NIMBLE FRAMEWORK 4
FEATURE PRIORITISATION
FEATURE PRIORITISATION
1 REVIEW THE FEATURE LIST TO ENSURE THAT EACH FEATURE IS CLEARLY UNDERSTOOD
2 UNDERTAKE SooM ANALYSIS TO IDENTIFY OUTLIERS
3 BREAKDOWN OUTLIERS INTO CONSTITUENT PARTS SO THEY FIT IN THE SooM
ASSESS
SooM -> Similar order of Magnitude
COST-> 50p 贈1 贈3 贈8 贈35 $25,000
The Frrrozen Haute Chocolate is unveiled at the Serendipity-3 restaurant in New York November 7, 2007 after Guinness
World Records researchers determined the $25,000 frozen hot chocolate was the most expensive dessert in the world
ESTIMATE-> OutlierMinimal Low Medium High Massive
NIMBLE FRAMEWORK 5
FEATURE PRIORITISATION
? DOES THE FEATURE ALIGN TO PRODUCT PURPOSE
? DOES IT SATISFY A NEED OF EITHER PRIMARY, SECONDARY OR TERTIARY USERS
? DOES IT HELP IMPLEMENT ONE OF THE FOUNDATION ATTRIBUTES OF THE PRODUCT
QUALIFY
? DOES IT SUPPORT OR ENHANCE A PRODUCT FUNCTION
? CAN THE FEATURE SUCCESS BE MEASURED - OR -
DOES IT SATISFY ONE OF THE SUCCESS MEASURES
NIMBLE FRAMEWORK 6
FEATURE PRIORITISATION
1 CALL A 60 secs VROOM MEETING WITH THE ENGINEERING TEAM
 VROOM -> Very Rough Order Of Magnitude
2 CLASSIFY AND SCORE EACH FEATURE FOR THE EFFORT REQUIRED TO IMPLEMENT
 Minimal (1)  Low (2)  Medium (3)  High (4)  Massive (5)
EFFORT
3 IF ANY FEATURE REQUIRES MORE THAN 60 secs to VROOM , IT NEEDS MORE CLARITY
 GOES BACK TO BACKLOG
4 IF AN OUTLIER IS FOUND  IT NEEDS TO BE BROKEN INTO CONSTITUENT PARTS
 GOES BACK TO BACKLOG
NIMBLE FRAMEWORK 7
FEATURE PRIORITISATION
O CLASSIFY EACH FEATURE ON THE BASIS OF USER VALUE GENERATED BY THE FEATURE
1 USER VALUE = IMPACT ON ONE USER x USER REACH
 User = Primary, Secondary, Tertiary or a combination
VALUE
2 CLASSIFY AND SCORE USER IMPACT ON ONE USER AS
 Minimal (1)  Low (2)  Medium (3)  High (4)  Massive (5)
3 CLASSIFY AND SCORE USER REACH (OVER A GIVEN PERIOD: 1 Day, 1 Week, 1 Month) AS
 Minimal (1)  Low (2)  Medium (3)  High (4)  Massive (5)
4 CALCULATE SCORE OF USER VALUE = IMPACT x REACH
 Minimal (1-5)  Low (6-10)  Medium (11-15)  High (16-20)  Massive (21-25)
NIMBLE FRAMEWORK 8
FEATURE PRIORITISATION
PLOT
TOP PRIORITY ITEMS RE-EVALUATE
1-2 4-5
WISH LIST PARKING-LOTLOW VALUE
LOW EFFORT HIGH EFFORT
Re-assess Placement on this Matrix
1-10
Use these as fillers Move to the Bottom of the Backlog
PRODUCT FEATURE PRIORITISATION - PRODUCT: XYZ
Build Feature MVP, Iterate, Improve or Discard
No Brainer - let us do them
Re-assess Business Benefits
Optimise Solution Options
Optimise Scope (too optimistic or Complex)
HIGH VALUE
16-25
Picked up as part of something bigger
Picked up to fill small gaps in Sprint Schedule
MEDIUM
PRIORITY
ITEMS
NIMBLE FRAMEWORK 9
FEATURE PRIORITISATION
FEATURE PRIORITISATION TOOL
NIMBLE FRAMEWORK 10
<---------> <--------->
INVESTMENT
1 Feature-1 Minimal Minimal Minimal Minimal WISH-LIST
2 Feature-2 Minimal Minimal Low Minimal WISH-LIST
3 Feature-3 Minimal Minimal Medium Minimal WISH-LIST
14 Feature-14 Minimal Medium High Medium MEDIUM-PRIORITY
15 Feature-15 Minimal Medium Massive Medium MEDIUM-PRIORITY
18 Feature-18 Minimal High Medium Medium MEDIUM-PRIORITY
19 Feature-19 Minimal High High High TOP-PRIORITY
20 Feature-20 Minimal High Massive High TOP-PRIORITY
25 Feature-25 Minimal Massive Massive Massive TOP-PRIORITY
53 Feature-53 Medium Minimal Medium Minimal PARKING-LOT
54 Feature-54 Medium Minimal High Minimal PARKING-LOT
55 Feature-55 Medium Minimal Massive Minimal PARKING-LOT
99 Feature-99 High Massive High High RE-EVALUATE
100 Feature-100 High Massive Massive Massive RE-EVALUATE
119 Feature-119 Massive High High High RE-EVALUATE
NIMBLE FRAMEWORK
PRODUCT PRIORITISATION MODEL - PRODUCT: XYZ
<---------------------------USER INPUT ----------------------------------------------------------------->
SEQ FEATURE NAME
BUSINESS VALUE SUGGESTED PRIORITY
MODEL QUADRANTEFFORT IMPACT REACH VALUE
THANK YOU
NIMBLE FRAMEWORK 11

More Related Content

Feature Prioritisation - NIMBLE FRAMEWORK

  • 1. NIMBLE FRAMEWORK FEATURE PRIORITISATION PRACTICAL PRODUCT MANAGEMENT SERIES MANOJ AGARWAL & TEAM
  • 2. TOPICS HOW TO DEFINE A PRODUCT PRIORITISATION - To be or not to be User Needs and wants and Struggles Identify user needs - why do we need the product VROOM - The art of sizing Ask the question Why? Ask the question Why 5 times What is Product Management and what it is not User centric product design Data enabled product design A/B testing and the 'C' How to eat the elephant Art of trialing a Product MVP Demystified External guest speakers - ad-hoc schedule Define the product concept The One Thing Untangle the spaghetti Creating a Product roadmap How to write great user stories MVP or PoC or Prototype - myths Demystified How to measure and iterate and discard Importance of Meaningful User Actions and how to capture them How to run a successful design sprint How UX Design integrates with Agile and Scrum Demystified - if we build it they will come Microservices as a Product Product of products NIMBLE FRAMEWORK 2
  • 3. FEATURE PRIORITISATION OBJECTIVE: I WANT TO BE ABLE TO PRIORITISE FEATURES OF MY PRODUCT USING A SIMPLE METHOD NIMBLE FRAMEWORK 3
  • 4. NIMBLE FRAMEWORK 4 FEATURE PRIORITISATION
  • 5. FEATURE PRIORITISATION 1 REVIEW THE FEATURE LIST TO ENSURE THAT EACH FEATURE IS CLEARLY UNDERSTOOD 2 UNDERTAKE SooM ANALYSIS TO IDENTIFY OUTLIERS 3 BREAKDOWN OUTLIERS INTO CONSTITUENT PARTS SO THEY FIT IN THE SooM ASSESS SooM -> Similar order of Magnitude COST-> 50p 贈1 贈3 贈8 贈35 $25,000 The Frrrozen Haute Chocolate is unveiled at the Serendipity-3 restaurant in New York November 7, 2007 after Guinness World Records researchers determined the $25,000 frozen hot chocolate was the most expensive dessert in the world ESTIMATE-> OutlierMinimal Low Medium High Massive NIMBLE FRAMEWORK 5
  • 6. FEATURE PRIORITISATION ? DOES THE FEATURE ALIGN TO PRODUCT PURPOSE ? DOES IT SATISFY A NEED OF EITHER PRIMARY, SECONDARY OR TERTIARY USERS ? DOES IT HELP IMPLEMENT ONE OF THE FOUNDATION ATTRIBUTES OF THE PRODUCT QUALIFY ? DOES IT SUPPORT OR ENHANCE A PRODUCT FUNCTION ? CAN THE FEATURE SUCCESS BE MEASURED - OR - DOES IT SATISFY ONE OF THE SUCCESS MEASURES NIMBLE FRAMEWORK 6
  • 7. FEATURE PRIORITISATION 1 CALL A 60 secs VROOM MEETING WITH THE ENGINEERING TEAM VROOM -> Very Rough Order Of Magnitude 2 CLASSIFY AND SCORE EACH FEATURE FOR THE EFFORT REQUIRED TO IMPLEMENT Minimal (1) Low (2) Medium (3) High (4) Massive (5) EFFORT 3 IF ANY FEATURE REQUIRES MORE THAN 60 secs to VROOM , IT NEEDS MORE CLARITY GOES BACK TO BACKLOG 4 IF AN OUTLIER IS FOUND IT NEEDS TO BE BROKEN INTO CONSTITUENT PARTS GOES BACK TO BACKLOG NIMBLE FRAMEWORK 7
  • 8. FEATURE PRIORITISATION O CLASSIFY EACH FEATURE ON THE BASIS OF USER VALUE GENERATED BY THE FEATURE 1 USER VALUE = IMPACT ON ONE USER x USER REACH User = Primary, Secondary, Tertiary or a combination VALUE 2 CLASSIFY AND SCORE USER IMPACT ON ONE USER AS Minimal (1) Low (2) Medium (3) High (4) Massive (5) 3 CLASSIFY AND SCORE USER REACH (OVER A GIVEN PERIOD: 1 Day, 1 Week, 1 Month) AS Minimal (1) Low (2) Medium (3) High (4) Massive (5) 4 CALCULATE SCORE OF USER VALUE = IMPACT x REACH Minimal (1-5) Low (6-10) Medium (11-15) High (16-20) Massive (21-25) NIMBLE FRAMEWORK 8
  • 9. FEATURE PRIORITISATION PLOT TOP PRIORITY ITEMS RE-EVALUATE 1-2 4-5 WISH LIST PARKING-LOTLOW VALUE LOW EFFORT HIGH EFFORT Re-assess Placement on this Matrix 1-10 Use these as fillers Move to the Bottom of the Backlog PRODUCT FEATURE PRIORITISATION - PRODUCT: XYZ Build Feature MVP, Iterate, Improve or Discard No Brainer - let us do them Re-assess Business Benefits Optimise Solution Options Optimise Scope (too optimistic or Complex) HIGH VALUE 16-25 Picked up as part of something bigger Picked up to fill small gaps in Sprint Schedule MEDIUM PRIORITY ITEMS NIMBLE FRAMEWORK 9
  • 10. FEATURE PRIORITISATION FEATURE PRIORITISATION TOOL NIMBLE FRAMEWORK 10 <---------> <---------> INVESTMENT 1 Feature-1 Minimal Minimal Minimal Minimal WISH-LIST 2 Feature-2 Minimal Minimal Low Minimal WISH-LIST 3 Feature-3 Minimal Minimal Medium Minimal WISH-LIST 14 Feature-14 Minimal Medium High Medium MEDIUM-PRIORITY 15 Feature-15 Minimal Medium Massive Medium MEDIUM-PRIORITY 18 Feature-18 Minimal High Medium Medium MEDIUM-PRIORITY 19 Feature-19 Minimal High High High TOP-PRIORITY 20 Feature-20 Minimal High Massive High TOP-PRIORITY 25 Feature-25 Minimal Massive Massive Massive TOP-PRIORITY 53 Feature-53 Medium Minimal Medium Minimal PARKING-LOT 54 Feature-54 Medium Minimal High Minimal PARKING-LOT 55 Feature-55 Medium Minimal Massive Minimal PARKING-LOT 99 Feature-99 High Massive High High RE-EVALUATE 100 Feature-100 High Massive Massive Massive RE-EVALUATE 119 Feature-119 Massive High High High RE-EVALUATE NIMBLE FRAMEWORK PRODUCT PRIORITISATION MODEL - PRODUCT: XYZ <---------------------------USER INPUT -----------------------------------------------------------------> SEQ FEATURE NAME BUSINESS VALUE SUGGESTED PRIORITY MODEL QUADRANTEFFORT IMPACT REACH VALUE