Abstract: Hey, psst!? Are you Continuously Deploying yet? You know everybody is doing it, right?
Why?
Some to go faster. Some to increase quality. Some because, let’s face it, it’s a really cool buzzword.
But let’s talk about what the real reason is. Should be. The control necessary to do Hypothesis Driven Development. Or, as I like to call it: Test First Product Management.
With the popularity of Lean Startup, we’ve seen a significant uptake in these kinds of business experiments. But how does it work in practice? We need feature toggles, A/B testing, analysis tools, and more? That sounds difficult. How do we get started today?
In this talk I’ll go through some examples, showing how to build a simple system that allows you to start with HDD right now, by coding it right on stage. And while coding the solution I'll also explain how to structure your process to support these experiments, with concrete examples I've used in the field.
Learning Outcomes: - What is Hypothesis Driven Development?
- What should an Agile process look like for HDD? How do you get there from Scrum?
- What does a hypothesis look like? How does it replace a story?
- How do we implement the hypothesis? Basic feature toggles and A/B testing.
- How do we keep track of the experiment’s results?
- How can we start with one simple test next sprint, without a big investment in tooling?
Attachments:
