reverse chaos method of requirements prioritisation
TRANSCRIPT
Reverse Chaos Method of Requirements Prioritisation
Gena Drahun
Gena Drahun [ˈɡə-na dra-ˈgün]
More than 100 design projects…
Experience with small projects…
Experience with large projects… • Failed: 75% (3 of 4) • Great success: 25% (1 of 4)
Chaos Manifesto Standish Group
Chaos Report, Standish Group
Study of
Project Success
Successful 76%
Challenged 20%
Failed 4%
Success Rates of Small* projects
* Less than $1 million in labor content
Challenged 52% Failed
38%
Successful 10%
Success Rates of Large* projects
* More than $10 million in labor content
Large Projects vs. Small Projects
• 10x times more decisions to made
• 7,5x lower success rate
Can we make less decisions and provide the same customer value?
Study of
Features Used
Hardly or never 50%
SomeFmes or occasionally
30%
OHen 20%
Usage of Implemented Features
Not implemented
33%
Hardly or never used
33%
Used someFmes or infrequently
20%
Used oHen 14%
Planned Features
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/
… 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/
Reverse Chaos
Scope of a Sample Product: • 90 Features • ~ 900 User Stories
Let’s apply the statistics from Chaos Report
14% Features will be used often
(1 feature of 7 planned)
Select <N1> features that you will be using (expect to be used) often
Closed Card Sorting: • Individual/ Group Sorting • with Product Team/ Users/ Business
MFP? Minimum Functional Product
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
20% features will be used sometimes
(1 feature of 5 planned)
From the features left, select <N2> features that you will be using (expect to be used) sometimes
Second round of Card Sorting
“Optimal” Product scope?
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
THINK WORK SMARTER NOT HARDER
Almost the
END
MVP
Who of you know what is MVP?
Are you sure?
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/
.
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
.
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).
hLp://www.mindtheproduct.com/2014/10/lean-‐product-‐management-‐the-‐mvp-‐culture-‐within-‐every-‐featureenhacement-‐development/
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.
One step further?
MVF Minimum Viable Feature
hLp://www.mindtheproduct.com/2013/05/the-‐minimally-‐viable-‐feature-‐approach/
You can set the level of “perfection” per individual feature
Choose the quality of your product ingredients
* Stephen Anderson’s Experiences Pyramid
Meaningful
Pleasurable
Usable
FuncFonal
Gena Drahun @HDrahun
hienadzdrahun
http://www.slideshare.net/Hienadz.Drahun
Add More Brains!