It is common to make an assertion, based on an assumption that is believed to be true, and where we do not have enough evidence to know for sure whether the assertion is true. And, to be considered a valid scientific hypothesis, it must also be possible to test the assertion. In agile product development, a common way to frame a hypothesis is to: define a desired outcome; express how we believe the outcome can be achieved; and articulate how we will know whether we achieved the outcome. By way of example, in Scrum, each iteration (Sprint) is a controlled (time-bounded) experiment, where each epic, and its child user stories, forms a hypothesis that helps align the members of teams and teams on the desired outcomes.
Authored by Steve Moubray
Edited by Philip Rogers
Photo by Mohamed Nohassi on Unsplash
Agile World Resources are provided as free resources to anyone seeking to learn more and are shared under a creative commons attribution license. This means if you use a resource elsewhere you must name Agile World Publishing as the source, who the author is, and the photo creator (if used).