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/
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/
- How is work measured traditionally? By output?
- How is success defined conventionally? Success is commonly defined as shipping a product, feature or bug fix to customers.
- How many companies are thinking into better practices?
- How far behind are conventional approaches?
- To ship more frequently Agile is adopted in modern thinking. However disruptors are delivering updates in one day based on analytics.
- 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.
- Classic agile is: plan, build, deploy, listen and repeat.
- Often it is pervasive culture that presents a bigger hurdle to success than technology.
- 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.