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

1. Building the Right Things Right?
We Can Do Both With Continuous
Business Goal Validation.
Hylke Stapersma & Niels Talens

2. After continuous integration
there is continuous
validation
Hylke Stapersma & Niels Talens

3. Hylke
Stapersma Software craftsman
@hylke1982

4. Niels Talens Agile consultant
@nielstalens

8. The goalless display

10. What's changing?

11. Customer focussed

12. Annual releases
- Supplier defines
- Big design upfront
3 Monthly
- Sliced design
upfront
- Slightly more
prioritized
1980 2010 Toda
y
Daily releases
- Hypothesis/experiment
s
- Quick feedback
- Data driven
1995
From push to pull
Weekly
- MVP based
- Strongly
prioritized
Product push Customer centric Relationship centric

13. Exponential growth of the impact of
software:

14. Business agility & tech speed

15. We live in a fast feedback
economy

16. ● no feedback/not acting on
feedback
The threat is:

17. Building the things right

19. Where we focus on...

20. ...where we often end up

21. Are we making the right
things?

22. Crap in - crap out

23. Feature gluttony

24. Unused features

25. Continuous validation

26. A backlog is not the
starting point. Objectives
are.

27. A deployment is not the
end. It's the beginning.

28. Business case
Product vision
Roadmap/backlog Minimal Viable Product Development
Impact map
Validation
Objectives Input Output Outcomes
Continuous validation

29. Objectives
Business case,
Business goals,
Product vision,
Impact mapping,
What is the desired outcome,
A lot of assumptions,

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.

31. Continuous validation &
impact mapping

32. Assumption Assumption Assumption
impactmapping.org

33. Continuous validation &
A/B testing

34. http://unbounce.com/
A B
C

35. OR
behave.org

36. vwo.com

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.

38. Right things
Or things right ?

39. Build the right things right
Why choose?

40. Meet Gareth...
...he’s seriously unpleasant

41. Meet Gareth
Seriously unpleasant
Open-Source
Validation of the WHY
Inspired by Cucumber
Facilitates collaboration
Written in Java, but ambition to
implement more languages

43. Objective phase
Define future goals
Formulate a hypothesis
Every objective can be defined as
experiment
Define experiments in a structured
manner
Backlog refinement

44. Objective phase

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

47. Output phase

48. Outcome phase
Running your experiment
Validate your hypothesis
Perform success/failed action
And act...

49. DEMO

50. Create experiment
• Plain text / readable for everybody
• Structured
• Result actions

51. Refine experiment
• Get input from different roles
• More process than tool (continuous
validation concept)

52. Define code for experiment
• Glue code
• Structure of experiment
• Act

53. Run experiment
• Validate your hypothesis
• Perform success/failed action

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)

55. Source code
•https://github.com/craftsmenlabs/xpdays
-bicycle-shed-continuous-validation
•https://github.com/craftsmenlabs/xpdays
-bicycle-shed
•https://github.com/craftsmenlabs/gareth-
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