Augury's Journey Towards CD by Assaf Mizrachi @Agile Israel 2019

1. Augury Journey Towards CD
AgileSparks
May 2019

2. Augury Confidential
COLLECT
Smart sensors monitor
your machines 24/7
ANALYZE
Algorithms predict
malfunctions and provide
alerts
VISUALIZE
Full visibility of machine
health across your facilityPREDICT
MACHINE
FAILURES

3. Augury Confidential

4. 65,000+ Machines
5,000+ Facilities

5. R&D Structure

6. Tech Stack

7. Augury Confidential
2 Years Ago...

8. SunSun
Squad B
Sun
Squad CSquad A Squad D
Wed Wed Wed
Squad A
Squad B
Squad D
Unite QA
Effort
Manual Regression Manual Regression
Release Trains

9. Release Version XXX
Release Version XXX + 1

10. Ice Cream Cone Anti-Pattern

11. Development
Release

12. Local Env
Squad Env
CI
Staging
1
2
3
4
5
6
Production
Release Process
Development Process

13. Quality
Deployment
Design
Too Many Handoffs During Development

14. Augury Confidential
Developer In The Center

15. What to
build??
How to
build??
Is it
working??
Is it deployed
yet??
How is it in
production?

16. Take active part in
shaping impactful
product
Design & Write
clean, simple and
testable code.
Own code quality
Deliver to Production
Monitor and track
deliverables behaviour and
usage

17. Developer Growth
==
Shorter High Quality Delivery Cycles

18. Fast and Safe Development.
Developer Growth.
Data Driven.
Fast Feedback Loop In Every Step.

19. Augury Confidential
Phase 1 - Built-In Quality
Development
Release

20. Developers Own Quality.
QA = Quality Assistance != Quality Assurance

21. Better Design Process

22. Code Reviews As Part of CI

24. Augury Confidential
Phase 2 - Break It, Ship It
Break It Ship It
Closer to Production

25. Break It down into smaller pieces
In order to eliminate release idea, reduce delivery risk and achieve a faster feedback loop, we
should breakdown feature into small decoupled, testable and shippable units.
Once a unit is implemented and tested it should be deploy to production by the developer.
Each delivered unit can have immediate or “eventual” impact

26. Closer to production
Once the developer ships code frequently into production, monitoring code’s behaviour in
production becomes a habit which is streamlined into the development life-cycle.
Receiving fast feedback from the production environment is extremely powerful practice.
Closer to Production

27. Separate deployment from release
By using tools such as feature flags we can avoid code aggregation in branches which is bad
practice.
The ability to integrate our code into production with limited activation is powerful tool and
enabler for actual testing in production.

28. Augury Confidential
Delivery Metrics

31. Augury Confidential
Key Learnings

32. ● Developers can do QA to their own code.
● Sharing half-baked things is not easy for most of developers
● Wonderful things happens when developers are minutes from production
● Developers feels more impactful and skilled since we moved to CD

33. Augury Confidential
Nowadays..

34. Continuous Delivery

35. Augury Confidential
THE END
Questions?