Toggle Menu

Don’t Assume You’re Creating Value, Prove it

By Mathias Eifert

Does your organization find it hard to determine “the right thing” to build? You are not alone – Agile methods offer few guidelines on how to translate organizational goals and customer needs into the backlog’s content and priorities, so there is a significant risk that Agile teams end up building “the wrong thing right.”

Approaching product development as a series of hypotheses about customers’ behaviors and value perceptions allows us to expand the scope of Agile’s “inspect and adapt” feedback loops to systematically identify and validate critical assumptions about our product’s value proposition. We also discuss ways to derive testable assumptions to enable validated learning, as well as implications on project planning and budgeting.

You Might Also Like

Agile

Is SAFe Agile? The Case for SAFe

I’m new to Agile, relatively speaking. I first heard of it only five years ago....

Agile

BDD (Behavior-Driven Development), Is it for me?

Would you like to develop products in a way that helps you discover users’ real...

Agile

Improving Scrum Teams with Visual Backlog Refinement

Many Scrum teams focus on the established five scrum events that take place each sprint...