Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

What testers can learn from brewing beer - Brewing beer the agile way

396 views

Published on

Knowing the bigger picture of your product development is important information to a software tester. Bram and I show you by the example of brewing beer how important this is. As a result the beer Breyk was launched at the Agile Testing Days 2016 and was welcomed with a rating of 4 (out of 5) in untappd.

Published in: Software
  • Be the first to comment

  • Be the first to like this

What testers can learn from brewing beer - Brewing beer the agile way

  1. 1. Brewing The agile way Eddy Bruin A story about beer development and tasting Bram Bronneberg
  2. 2. Eddy Bruin Bram Bronneberg
  3. 3. Once upon a time…
  4. 4. The perfect beer for ATD
  5. 5. Where to start? Market research!
  6. 6. Checking the basics
  7. 7. What type of beers? Altbier Berliner Weisse Bock Dampfbier Doppelbock Dunkel Eisbock Gose Helles Kellerbier Kölsch Kottbusser Maibock Malt beer Märzen Pilsner Rauchbier Roggenbier Schwarzbier Weissbier Zoigl Pilsner 68% Weissbier 10% Schwarzbier 2%
  8. 8. What do germans like? Sweetspot Between Alcohol 5,1 and 5,6%
  9. 9. So what does this all tell us?
  10. 10. So we present you!!! <Breyk> Type: Rye pale ale Estimated OG: Cat. I – 1,050 (12,5⁰ P) Estimated FG: 1,007 (2⁰ P) Bitterness: 26 EBU/IBU Color: EBC: 16 / SRM: 8
  11. 11. Features ≠User Experience #1
  12. 12. Brewing The agile way A story about beer development and tasting A story about product development and testing
  13. 13. The brewing process our first batch
  14. 14. Milling
  15. 15. Mashing
  16. 16. Lautering
  17. 17. Boiling
  18. 18. Cooling
  19. 19. Fermenting
  20. 20. Packaging
  21. 21. Brewing a prototype
  22. 22. Brewing a prototype You might not need to have a big infrastructure to test the business value of your idea #2
  23. 23. Testing our prototype
  24. 24. How did we test?
  25. 25. Source: Gojko Adzic Did we look at all levels of quality?
  26. 26. Testing our prototype
  27. 27. Traditional Test Focus
  28. 28. New product? Test business assumptions over functional quality #3
  29. 29. Prototype #2 and evolution Feedback Improvement Lacking “nose” Reducing boiling time of hops Strange sweetness Use different dry hops To little carbonation Increasing bottle sugar Lighter taste color than expected Increase the Rye content
  30. 30. • Science behind the recipe • Calculated Bitterness • Calculated Color • Calculated Alcohol percentage • Science behind the brewing • Mashing steps • Evaporation+purching • Science behind the water! Putting the craft in to craftsmanship
  31. 31. Predicting beer color
  32. 32. Predicting beer bitterness IBUs = U% * (ALPHA% * W_OZ * 0.7489) (V_Gal)
  33. 33. Beer brewing is empirical and a craftsmanship that NOT just everybody can do #4
  34. 34. The Final Batch x 40 Maintainability Compliancy
  35. 35. Context can change quality expectations #5
  36. 36. What can testers learn from brewing beer? Features ≠ User Experience The user’s experience will lead to success or failure You might not need to have a big infrastructure to test the business value of your idea Find out if you need to integrate with a big infrastructure from the beginning New product? Test business assumptions over functional quality Determine what makes the project a success and test for this first Beer brewing/Testing is empirical and a craftsmanship that NOT just everybody can do From repetition and experimentation one gains mastery Context can change quality expectations Not all quality attriubutes are equally important in a certain point of time
  37. 37. Big thanks to …
  38. 38. <Br>eaking <Br>ewery
  39. 39. Hey, we just met you And this is crazy So here’s our twitter So tweet us maybe?! @eddybruin eddy@loopforward.nl bram.bronneberg@polteq.com @brambronneberg

×