Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Agile Product
Ownership
Dr. David Michel
david.michel@tessella.com
@DavMichel76
Quick questions
before we start…
What’s your definition of success?
Feature
A
Feature
B
Feature
C
Are you running a Feature Factory ?
Declaring Victory
Too Soon
Scope On Time Outcome Win?
Great Landing,
Wrong airport.
Questions we are interested in…
• Did this deliver value to the customer?
• What impact did it have on their business?
• A...
EPIC
Features
Mr. Product Owner
The Team
The conversations should include:
• How do we assess the impact on
the business?
...
Where does
the Product
Backlog
come from?
Tim
e
# stories
Stories when created
Stories when developed/done
• The PO knows what ought to
be developed up front.
• The...
Tim
e
# stories
Stories when created
Stories when developed/done
• The dev team works on the
easier first, leaving the
har...
Backlog with stories of different size
and level of refinement
Priority
• Useful for the dev team to have
the highest prio...
Tim
e
# stories That’s the ideal curve, when
the Product Owner knows
what he/she is doing
When you’re constantly
learning ...
Tim
e
# stories
Stories when they are created
Stories when are developed/done
• You need something else to
measure progres...
22
Kano Model
You’ll need more than a simple backlog!
24
Value Proposition Canvas
25
Value Proposition Canvas
Story Mapping
Story Mapping
Impact Mapping
Impact Mapping
The product-shaped hole
Where does
the Product
Backlog
come from?
Requirements
or
Product Design
Decisions
If it’s your decision, it’s design.
If it’s not, it’s a requirement
“
”
Product design decisions
need to be tested & validated
Just like technical ones are
Discovery
Delivery
Figuring out
what to build
Then build it
• No validation of product design decisions
• Which are all ma...
37
Dual Track Agile
38
Dual Track Agile
http://www.jpattonassociates.com/dual-track-development/
• Pay-to-learn: iterative,
innovative, discovery,
deliverables = learning
outcomes
• Build-value:
incremental, progress
me...
How do you validate the learning?
Minimal Viable Product
Experiment
Effort
Effort
Effort
Confidence
Lunch
Holiday
Car
House
Effort
Confidence
Lunch
Holiday
Car
House
Effort
Confidence
Lunch
Holiday
Car
House
Stupid &
Expensive
Stupid &
Wasting time
Effort
Confidence
Lunch
Holiday
Car
House
Stupid &
Expensive
Stupid &
Wasting time
These are
all MVE
tests!
Effort
Confidence
Lunch
Holiday
Car
House
Stupid &
Expensive
Stupid &
Wasting time
These are
all MVE
tests!
Learning from user interviews
?
Agile Product Ownership
Agile Product Ownership
Agile Product Ownership
Agile Product Ownership
Agile Product Ownership
Agile Product Ownership
Agile Product Ownership
Agile Product Ownership
Upcoming SlideShare
Loading in …5
×

Agile Product Ownership

Slides from the meetup:
https://www.meetup.com/Agile-Oxfordshire/events/256247736/

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all
  • Be the first to comment

Agile Product Ownership

  1. 1. Agile Product Ownership Dr. David Michel david.michel@tessella.com @DavMichel76
  2. 2. Quick questions before we start…
  3. 3. What’s your definition of success?
  4. 4. Feature A Feature B Feature C Are you running a Feature Factory ?
  5. 5. Declaring Victory Too Soon
  6. 6. Scope On Time Outcome Win?
  7. 7. Great Landing, Wrong airport.
  8. 8. Questions we are interested in… • Did this deliver value to the customer? • What impact did it have on their business? • Are they actually using the software? • Are we building the right thing? • Are we on track? • How are we doing in terms of budget? • Will we be able to finish in time?
  9. 9. EPIC Features Mr. Product Owner The Team The conversations should include: • How do we assess the impact on the business? • How do we judge whether this was the right thing to build?
  10. 10. Where does the Product Backlog come from?
  11. 11. Tim e # stories Stories when created Stories when developed/done • The PO knows what ought to be developed up front. • The dev team works on hardest/riskiest items first, leaving the easier ones for later (so they are faster at the end) • Predicted end date converges to the left has time passes.
  12. 12. Tim e # stories Stories when created Stories when developed/done • The dev team works on the easier first, leaving the hardest/riskiest for later… • Culture where team is desperate to appear busy? • End date every hard to predict
  13. 13. Backlog with stories of different size and level of refinement Priority • Useful for the dev team to have the highest priority items as the smallest, and most refined items • BUT, the fact that a story is unclear does not mean is has low value or is not important! • Those stories should perhaps be the ones to be worked on sooner rather than later! • The criteria for priority should be value/risk, not “known”
  14. 14. Tim e # stories That’s the ideal curve, when the Product Owner knows what he/she is doing When you’re constantly learning from feedback (i.e. when you are agile)
  15. 15. Tim e # stories Stories when they are created Stories when are developed/done • You need something else to measure progress – Cannot tell when you’ll be finished • You need to become value- driven, with different kind of metrics
  16. 16. 22 Kano Model
  17. 17. You’ll need more than a simple backlog!
  18. 18. 24 Value Proposition Canvas
  19. 19. 25 Value Proposition Canvas
  20. 20. Story Mapping
  21. 21. Story Mapping
  22. 22. Impact Mapping
  23. 23. Impact Mapping
  24. 24. The product-shaped hole
  25. 25. Where does the Product Backlog come from?
  26. 26. Requirements or Product Design Decisions
  27. 27. If it’s your decision, it’s design. If it’s not, it’s a requirement “ ”
  28. 28. Product design decisions need to be tested & validated Just like technical ones are
  29. 29. Discovery Delivery Figuring out what to build Then build it • No validation of product design decisions • Which are all made up front
  30. 30. 37 Dual Track Agile
  31. 31. 38 Dual Track Agile http://www.jpattonassociates.com/dual-track-development/
  32. 32. • Pay-to-learn: iterative, innovative, discovery, deliverables = learning outcomes • Build-value: incremental, progress metrics = # stories completed • Trim-the-tail: Kanban, refinement before a release Disciplined Learning: Risk Reduction = Knowledge Acquisition
  33. 33. How do you validate the learning? Minimal Viable Product Experiment
  34. 34. Effort
  35. 35. Effort
  36. 36. Effort Confidence Lunch Holiday Car House
  37. 37. Effort Confidence Lunch Holiday Car House
  38. 38. Effort Confidence Lunch Holiday Car House Stupid & Expensive Stupid & Wasting time
  39. 39. Effort Confidence Lunch Holiday Car House Stupid & Expensive Stupid & Wasting time These are all MVE tests!
  40. 40. Effort Confidence Lunch Holiday Car House Stupid & Expensive Stupid & Wasting time These are all MVE tests!
  41. 41. Learning from user interviews
  42. 42. ?

×