## When Should You Use a Hypothesis Instead of Just Building a Feature? Use a hypothesis when you're not certain a feature will add value. For essential features like login functionality, no hypothesis is needed—they're considered “table stakes.” But when value is uncertain, it's better to validate with an experiment. >[!metaphor] >Using a hypothesis for every feature is like taste-testing water before serving it at a restaurant. Standard necessities don’t need proof of value; they’re foundational.</br> >Hypotheses are best used when you're unsure a feature will deliver value—not when you’re covering the basics. ## Works Consulted 1. [An Explanation of Hypothesis-Driven Development](https://www.youtube.com/watch?v=R5CNZDPayRc&t=2s) | Scrum.org | Accessed 26 Dec. 2024. ## Connections follows:: [[5.2 Assumptions Become Experiments in Hypothesis-Driven Development]] topics:: [[Hypothesis-Driven Development]], [[Bet]], [[Experiment]], [[Hypothesis]] ![[Footer]]