Building the rights Right. Use the concept of continuous validation (hypothesis driven development) to prevent that your automated software development pipeline becomes a vehicle to deliver crap fast and helps you focus on the goals that software should help you achieve
30. Outcome
validation
Did we achieve our goals?
Were our assumptions right?
Are our previous assumptions right?
Great way to communicate with
stakeholders,
No no-impact features,
Create evidence based decisions.
37. Continuous validation:
We think by proving a form the amount of new
users will increase by 30% in the first month after
implementation.
A/B testing:
Let's see which variant of the form has more
conversion.
43. Objective phase
Define future goals
Formulate a hypothesis
Every objective can be defined as
experiment
Define experiments in a structured
manner
Backlog refinement
45. Input phase
Refine your experiment
Every role can give input for an
experiment
Achieve better understanding for
goals for every role
Backlog refinement
46. Output phase
Create a lab for your experiments
Define glue (code) that runs your
experiments
Define fail/success actions
54. Future of Gareth
•Move to Kotlin for experiment
management framework
•Continuous running experiments
•Server-Client model
•Support of definitions in any language
(not only JVM)
56. How can you contribute
•Use Gareth and gives us feedback
•Contribute code
•Spread the word
•http://getgareth.io/
57. Conclusions
• Build the right things AND build the
things right
•Automate the validation of goals
•Use a structure that is understandable for
everybody