Top Banner
Reverse Chaos Method of Requirements Prioritisation Gena Drahun
50

Reverse Chaos Method of Requirements Prioritisation

Jan 09, 2017

Download

Design

Gena Drahun
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Reverse Chaos Method of Requirements Prioritisation

Reverse Chaos Method of Requirements Prioritisation

Gena Drahun

Page 2: Reverse Chaos Method of Requirements Prioritisation

Gena Drahun [ˈɡə-na dra-ˈgün]

Page 3: Reverse Chaos Method of Requirements Prioritisation

More than 100 design projects…

Page 4: Reverse Chaos Method of Requirements Prioritisation

Experience with small projects…

Page 5: Reverse Chaos Method of Requirements Prioritisation

Experience with large projects… •  Failed: 75% (3 of 4) •  Great success: 25% (1 of 4)

Page 6: Reverse Chaos Method of Requirements Prioritisation

Chaos Manifesto Standish Group

Page 7: Reverse Chaos Method of Requirements Prioritisation

Chaos  Report,  Standish  Group  

Page 8: Reverse Chaos Method of Requirements Prioritisation

Study of

Project Success

Page 9: Reverse Chaos Method of Requirements Prioritisation

Successful  76%  

Challenged  20%  

Failed  4%  

Success Rates of Small* projects

* Less than $1 million in labor content

Page 10: Reverse Chaos Method of Requirements Prioritisation

Challenged  52%  Failed  

38%  

Successful  10%  

Success Rates of Large* projects

* More than $10 million in labor content

Page 11: Reverse Chaos Method of Requirements Prioritisation

Large Projects vs. Small Projects

•  10x times more decisions to made

•  7,5x lower success rate

Page 12: Reverse Chaos Method of Requirements Prioritisation

Can we make less decisions and provide the same customer value?

Page 13: Reverse Chaos Method of Requirements Prioritisation

Study of

Features Used

Page 14: Reverse Chaos Method of Requirements Prioritisation

Hardly  or  never  50%  

SomeFmes  or  occasionally  

30%  

OHen  20%  

Usage of Implemented Features

Page 15: Reverse Chaos Method of Requirements Prioritisation

Not  implemented  

33%  

Hardly  or  never  used  

33%  

Used  someFmes  or  infrequently  

20%  

Used  oHen  14%  

Planned Features

Page 16: Reverse Chaos Method of Requirements Prioritisation

Even if you have half your users asking for a feature it doesn’t necessarily mean they will actually use the feature. What people say they will do is often radically different from what they actually do.

hLp://www.mindtheproduct.com/2013/05/the-­‐minimally-­‐viable-­‐feature-­‐approach/  

Page 17: Reverse Chaos Method of Requirements Prioritisation

… there’s a much bigger problem… : people are often incapable of articulating why they do things or how they would behave in the future.

hLp://www.forbes.com/sites/rogerdooley/2012/10/04/market-­‐research/  

Page 18: Reverse Chaos Method of Requirements Prioritisation

Reverse Chaos

Page 19: Reverse Chaos Method of Requirements Prioritisation

Scope of a Sample Product: •  90 Features •  ~ 900 User Stories

Page 20: Reverse Chaos Method of Requirements Prioritisation
Page 21: Reverse Chaos Method of Requirements Prioritisation

Let’s apply the statistics from Chaos Report

Page 22: Reverse Chaos Method of Requirements Prioritisation

14% Features will be used often

(1 feature of 7 planned)

Page 23: Reverse Chaos Method of Requirements Prioritisation

Select <N1> features that you will be using (expect to be used) often

Page 24: Reverse Chaos Method of Requirements Prioritisation

Closed Card Sorting: •  Individual/ Group Sorting •  with Product Team/ Users/ Business

Page 25: Reverse Chaos Method of Requirements Prioritisation

MFP? Minimum Functional Product

Page 26: Reverse Chaos Method of Requirements Prioritisation

Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.  

Antoine de Saint-Exupéry  

Page 27: Reverse Chaos Method of Requirements Prioritisation

20% features will be used sometimes

(1 feature of 5 planned)

Page 28: Reverse Chaos Method of Requirements Prioritisation

From the features left, select <N2> features that you will be using (expect to be used) sometimes

Page 29: Reverse Chaos Method of Requirements Prioritisation

Second round of Card Sorting

Page 30: Reverse Chaos Method of Requirements Prioritisation

“Optimal” Product scope?

Page 31: Reverse Chaos Method of Requirements Prioritisation

hLp://www.jeffgothelf.com/blog/agile-­‐doesnt-­‐have-­‐a-­‐brain/#sthash.riyIEay3.dpbs  

Agile doesn’t have a brain. Bill Scott

… no mechanism for determining if they’re building the right feature.

Jeff Gothelf

Page 32: Reverse Chaos Method of Requirements Prioritisation

THINK  WORK  SMARTER  NOT  HARDER    

Page 33: Reverse Chaos Method of Requirements Prioritisation

Almost the

END

Page 34: Reverse Chaos Method of Requirements Prioritisation
Page 35: Reverse Chaos Method of Requirements Prioritisation

MVP

Page 36: Reverse Chaos Method of Requirements Prioritisation

Who of you know what is MVP?

Page 37: Reverse Chaos Method of Requirements Prioritisation

Are you sure?

Page 38: Reverse Chaos Method of Requirements Prioritisation

We define MVP as… unique product that maximizes return on risk for both the vendor and the customer.

.  

Frank Robinson Coined the term “Minimum Viable Product” in 2001

http://www.syncdev.com/minimum-viable-product/

Page 39: Reverse Chaos Method of Requirements Prioritisation

.  

Frank Robinson, Coined the term “Minimum Viable Product” in 2001

http://www.syncdev.com/minimum-viable-product/

* Hurdle rate is the minimum acceptable rate of return. Most companies use 12% hurdle rate.

*  

https://en.wikipedia.org/wiki/Minimum_acceptable_rate_of_return

Page 40: Reverse Chaos Method of Requirements Prioritisation

.  

Ash Maurya Author of “Running Lean” and creator of “Lean Canvas”

http://leanstack.com/minimum-viable-product//

Minimum Viable Product is the smallest thing you can build that delivers customer value (and as a bonus captures some of that value

back).

Page 41: Reverse Chaos Method of Requirements Prioritisation
Page 42: Reverse Chaos Method of Requirements Prioritisation

hLp://www.mindtheproduct.com/2014/10/lean-­‐product-­‐management-­‐the-­‐mvp-­‐culture-­‐within-­‐every-­‐featureenhacement-­‐development/  

Page 43: Reverse Chaos Method of Requirements Prioritisation

ED  

1  

2  

3  

Gena  Drahun,  September  2015  |  With  compliments  to  Jussi  Pasanen  and  Aaron  Walter  

Build the product small but complete, not by a part, by a slice or by a layer.

Page 44: Reverse Chaos Method of Requirements Prioritisation

One step further?

Page 45: Reverse Chaos Method of Requirements Prioritisation

MVF Minimum Viable Feature

hLp://www.mindtheproduct.com/2013/05/the-­‐minimally-­‐viable-­‐feature-­‐approach/  

Page 46: Reverse Chaos Method of Requirements Prioritisation

You can set the level of “perfection” per individual feature

Page 47: Reverse Chaos Method of Requirements Prioritisation

Choose the quality of your product ingredients

Page 48: Reverse Chaos Method of Requirements Prioritisation

*  Stephen  Anderson’s  Experiences  Pyramid  

Meaningful  

Pleasurable  

Usable  

FuncFonal  

Page 49: Reverse Chaos Method of Requirements Prioritisation
Page 50: Reverse Chaos Method of Requirements Prioritisation

Gena Drahun @HDrahun

hienadzdrahun

http://www.slideshare.net/Hienadz.Drahun

Add More Brains!