Methodology - Outcome Driven Development

Methodology - Outcome Driven Development

This outline is based off my understanding of the article
“Done is dead – welcome to outcome-driven development” found at:
https://sdtimes.com/agile/done-dead-welcome-outcome-driven-development/

1. How is work measured traditionally? By output?
2. How is success defined conventionally? Success is commonly defined as shipping a product, feature or bug fix to customers.
3. How many companies are thinking into better practices?
4. How far behind are conventional approaches?
5. To ship more frequently Agile is adopted in modern thinking. However disruptors are delivering updates in one day based on analytics.
6. Outcome-driven development defines “done” as delivering measurable value, not simply completing user stories. However shipping or delivering doesn’t realize impact to the user or customer.
7. Classic agile is: plan, build, deploy, listen and repeat.
8. Often it is pervasive culture that presents a bigger hurdle to success than technology.
9. Instead of measuring outputs of effort (hours worked, user stories shipped, etc.), the outcome-driven development team sets goals measured in results: reduced churn, improved Apdex score, more users returning each day, etc.