Download to read offline
Uploaded byLourenco P Soares
'Pierda Alcance Ahora! Preguntame Como!': Goal-based Priorization
This document discusses goal-based prioritization for product development. It presents an approach using independent streams of work aligned with business goals to validate hypotheses with minimal effort. Stories are plotted on a priority matrix based on user value and business value. The highest priority stories are those in the "Excel" category. Stories are pulled in small, finite increments to deliver working functionality and avoid scope creep. This ensures effort is focused on incrementally attaining goals through hypothesis validation.
More Related Content
Similar to 'Pierda Alcance Ahora! Preguntame Como!': Goal-based Priorization
'Pierda Alcance Ahora! Preguntame Como!': Goal-based Priorization
- 1. Goal-based Priorization Lourenço P.Soares | Alexandre Klaser
- 2.
- 3.
- 5.
- 6. Ok, but... ...if there’sno backlog, what is there?
- 7.
- 8.
- 9. Effort aligned to business goals Independent streamsof work Just enough to meet the goal
- 10.
- 11. Effort aligned tobusiness goals What’s the expected result when we implement a given functionality? How can we guarantee we are doing what must be done? http://www.flickr.com/photos/morganhh/
- 13. Once upon atime...
- 20. Independent streams ofwork What to do when a hypothesis is wrong or cannot be validated? How to prioritize streams of work and maintain business alignment? http://www.flickr.com/photos/elsie/
- 21.
- 22. Prioritized by value Uservalue High Low Low Business Value High
- 23. Prioritized by value Uservalue High Low Low Business Value High
- 24. Prioritized by value Uservalue High Low Low Business Value High
- 25. Prioritized by value Uservalue High Low Low Business Value High
- 26. Just enough tomeet the goal How to validate a hypothesis with the least possible effort? How to avoid that dependency between stories prevent progress in small increments? http://www.flickr.com/photos/pasukaru76/
- 27.
- 28.
- 29.
- 30. Hypothesis are likeonions
- 31. Satisfaction Kano Model Implementation Basic met ≠ not met = Adapted from: http://en.wikipedia.org/wiki/Kano_model
- 32. Satisfaction Kano Model Performance met = not met = Implementation Basic met ≠ not met = Adapted from: http://en.wikipedia.org/wiki/Kano_model
- 33. Excitement met = notmet ≠ Satisfaction Kano Model Performance met = not met = Implementation Basic met ≠ not met = Adapted from: http://en.wikipedia.org/wiki/Kano_model
- 36. Provide Levels of attainmentof goals Basic mechanics It is impossible to know if it is doable before validating this much You need to know it to use it
- 37. Provide Levels of attainmentof goals Basic mechanics It is impossible to know if it is doable before validating this much You need to know it to use it “It’s a proof of concept... Without this, the experience is broken... I would never go live with only this...”
- 39. Provide Basic mechanics It isimpossible to know if it is doable before validating this much You need to know it to use it Satisfy Levels of attainment of goals Basic functionality Meets user needs Anyone with minimum knowledge should be able to use it “It’s a proof of concept... Without this, the experience is broken... I would never go live with only this...”
- 40. Provide Basic mechanics It isimpossible to know if it is doable before validating this much You need to know it to use it “It’s a proof of concept... Without this, the experience is broken... I would never go live with only this...” Satisfy Levels of attainment of goals Basic functionality Meets user needs Anyone with minimum knowledge should be able to use it “All of our competitors have it... I would expect it to work... It’s something even my mom would understand...”
- 42. Provide Basic mechanics It isimpossible to know if it is doable before validating this much You need to know it to use it “It’s a proof of concept... Without this, the experience is broken... I would never go live with only this...” Satisfy Basic functionality Meets user needs Anyone with minimum knowledge should be able to use it “All of our competitors have it... I would expect it to work... It’s something even my mom would understand...” Excel Levels of attainment of goals Diferentiating proposition Only the main features of the product should be at this level Draw users to the product
- 43. Provide Basic mechanics It isimpossible to know if it is doable before validating this much You need to know it to use it “It’s a proof of concept... Without this, the experience is broken... I would never go live with only this...” Satisfy Basic functionality Meets user needs Anyone with minimum knowledge should be able to use it “All of our competitors have it... I would expect it to work... It’s something even my mom would understand...” Excel Levels of attainment of goals Diferentiating proposition Only the main features of the product should be at this level Draw users to the product “Only your product does this... Makes me come back time and time again... Everyone is talking about it...”
- 45.
- 46.
- 47.
- 48.
- 49.
- 50.
- 51.
- 52.
- 53.
- 54.
- 55.
- 56.
- 57.
- 58.
- 59.
- 60.
- 61.
- 62. It works inpractice…
- 63. The whole teamusing the board “It helps a great deal when finding the most important stories”
- 64.
- 65. Recaptulando... Further reading Beyond GoodEnough – Darius Kumana (bit.ly/darius_bge) Systemico Model – Barry O’Rilley & Lourenço P. Soares (bit.ly/systemico) Kano Model – Jason Mesut (bit.ly/kano_model) Replacing Requirements with Hypotheses– Josh Seiden (bit.ly/josh_hdd) INVEST in Good Stories, and SMART Tasks – Bill Wake (bit.ly/invest_stories) aklaser@thoughtworks.com @alklaser lous@thoughtworks.com about.me/lous