[VLOG] 4 Reasons Agile Teams Should Reject Hypothesis Driven Delivery

(United States)

April 6, 2021

When (Patricia Kong - Product Owner of Enterprise Solutions at Scrum.org) taught me how to combine the chocolatey-goodness of Evidence Based Management with the hazelnutty-goodness of Hypothesis Driven Delivery, I was ecstatic! "AHA!", I says to myself. "This is the missing piece that will unlock the gates leading to the path of Agility for all my clients!", says I. Alas, it was not to be :(

I was disabused of this naive notion by my students and clients. "Not so fast, compadre!", they said to me. "This kind of theoretical B.S. only works in the imaginary "Agile Trainer World" that you live in, Ravi. Not in the "actual real world" that we live in." So they became my trainers and taught me four reasons why Agile Teams should reject Hypothesis Driven Delivery.

Being a compulsive trainer, I promptly recorded a video to share what I learned and pay their kindness forward. Can you watch this video and tell me what you think...?

What did you think about this post?

Share with your network

Comments (2)

07:55 am April 7, 2021

It will be interesting to see what other experienced POs say about this thought provocative video. :-)

David Murphy

09:21 am April 27, 2021

It is a tool that can be valuable in some circumstances, but not for all development. It seems to me to be a valuable tool for marketing teams who would need an IT support team with them. This would have to be a highly empowered team, but in large corporates, where cost control and managerial command and control are so highly valued would be hard to make work. It allows to make small changes quickly that can bring real value, also it can help refine and define the problem domain prior to letting loose the main software delivery teams. It's advantage is a rapid feedback loop. I would see it as mostly wasteful in large scale software development once past project definition.