Experiment Driven Development
1 like1,393 views
The document discusses experiment-driven development in software engineering, emphasizing the importance of A/B testing to determine effective changes in web applications. It illustrates how a larger skip link on a signup page increased purchases by 5% without affecting new subscriptions. The author encourages the continuous cycle of proposing theories, conducting experiments, analyzing data, and iterating based on results.
Related topics:1 of 19
More Related Content
What's hot (20)
Ad
Viewers also liked (18)
Ad
Similar to Experiment Driven Development (20)
More from Mike Gehard (8)
Recently uploaded (20)
Experiment Driven Development
- 1. Experiment Driven Development The “real” engineering in software @mikegehard BS Chemical Engineering MS Software Engineering
- 2. How do you know that changes you make to your web application are the “right” ones?
- 4. It depends.
- 5. What makes or saves my company money?
- 6. Number of purchases Number of new subscriptions
- 7. What is your theory about that metric?
- 8. If you don’t know where you are going, how do you know when you get there?
- 9. By providing a larger skip link on the signup page, we will increase the number of purchases without sacrificing new subscriptions.
- 10. A/B Testing while collecting data
- 11. Analyze the data without bias.
- 12. Leave the egos at the door.
- 13. When compared to the control, the larger skip link increased purchases by 5% and did not decrease new subscriptions.
- 15. What’s next?
- 16. If you want to know why something happened then propose a new experiment to collect that data.
- 17. Repeat
- 18. Propose a theory about business metric(s) Experiment and measure those metrics Analyze the data and make a decision Iterate and prosper