Skip to main content

Focus on creating value through experimentation

Scrum Teams don’t know the value of the work they’ve done until they put it in the hands of their customers, until  then value is just an assumption. They might believe certain product features will be valuable for their customers, but they can only validate it when people are actually using it. That’s why Scrum Teams should take a hypothesis-driven approach and treat their work in a Sprint as experiments. 

As a Product Owner, encourage experimentation by using the Sprint as a short feedback cycle in which the Scrum Team has the opportunity to validate and test the assumptions they have about the product and customer needs. This reduces the risk of the Scrum Team building a product nobody wants or needs and allows the Product Owner to adapt the Product Backlog to maximize the value of the product. Being open to experimenting and adapting to evolving circumstances is key to maximizing product value based on continuous learning.

The Evidence-Based Management (EBM) framework can help Product Owners and Scrum Teams measure, manage and increase the value they derive from their product delivery.EBM helps teams to focus on improving outcomes, reducing risks, and optimizing investments. 

 


Resources:

Learning Series
Hypothesis-driven development offers a structured approach to problem-solving and innovation while minimizing risks, enabling evidence-based decisions, and fostering experimentation. This series includes the benefits of a hypothesis-drive approach for Scrum Teams and product delivery as well as templates and examples of different hypothesis formats.

 

Blog Post
The truth is, worrying about velocity is a trap: it says “we don’t care where we end up, so long as we get there fast.” That’s just wrong. Teams who measure their velocity but don’t or can’t measure customer outcomes may, quite simply, be driving in the wrong direction.
4.6 from 26 ratings


 


What did you think about this content?


Included In

Learning Series
This learning series highlights 9 ways a Product Owner can boost their effectiveness.