hypothesis-driven-development

At Spotify, we aim to build and improve our product in a data-informed way. To do that, teams are encouraged to generate and test hypotheses by running experiments and gathering evidence for what works and what doesn’t. 

tagged: spotifycroexperimenationhypothesis-driven-development

Remember back to the time when we were in high school science class. Our teachers had a framework for helping us learn – an experimental approach based on the best available evidence at hand. We were asked to make observations about the world around us, then attempt to form an explanation or hypothesis to explain what we had observed. We then tested this hypothesis by predicting an outcome based on our theory that would be achieved in a controlled experiment – if the outcome was achieved, we had proven our theory to be correct.

tagged: hypothesis-driven-developmentscience

Like agile, hypothesis-driven development (HDD) is more a point of view with various associated practices than it is a single, particular practice or process. That said, my goal here for is you to leave with a solid understanding of how to do HDD and a specific set of steps that work for you to get started.

tagged: hypothesis-driven-development

Continuous delivery demands the use of hypotheses, not requirements, to deliver what customers want. Developers embrace continuous experimentation and adaption.

tagged: hypothesis-driven-developmentcontinuous-delivery