How do you ship code faster and reliably without making sacrifices? Ben Mostafa shares actionable insights into driving DevOps practices in the real world.

1. Measuring and driving DevOps
practices in the real world
Measurement and motivation

2. What gets measured
gets done

3. Ben Mostafa
Engineering Manager &
Head of Developer
Relations

4. MessageMedia
API First Business
Messaging

5. API (MEL) API (SGN) API (NZ) Backend
Services (MEL)
Web (MEL)
Web (SGN) Web (SGN) Modules (MEL) Modules (SGN) Gateway (MEL) Gateway
(SYD)

6. Revisiting
DevOps principles
Flow
Always seeking
to increase flow
Feedback
Shorten & amplify
feedback loops
Learning &
Experimentation
Repetition &
Practice

7. Creating a
DevOps dashboard
Team 1 Team 2 Team 3 Team 4 Team 5
Change
Lead Time
Services
Health
Codebase
Health
Deployment
s

8. What to
measure?
Measure
deployments
Measure
change lead time
Codebase
health
Service
health

9. Deployments
What to measure?
1 Deployments per engineer
2 Deployment duration
3 Time of day
4 Deployment success/failure

10. 1 Deployments per engineer
2 Deployment duration
3 Time of day
4 Deployment success/failure
Deployments
What to measure?

11. 1 Deployments per engineer
2 Deployment duration
3 Time of day
4 Deployment success/failure
Deployments
What to measure?

12. 1 Deployments per engineer
2 Deployment duration
3 Time of day
4 Deployment success/failure
Deployments
What to measure?

13. Deployments
visualisations
Deployments
Mon Tue Wed Thu Fri
Date
TimeofDay
9am
12pm
3pm
6pm
9pm
Deployments by Engineers

14. Change lead time
What to measure?
1 Time spent in each step
2 Wait time between each step
3 Pull request metrics – time to close, reviewers/approvals, comments and
size

15. Change lead time
What to measure?
1 Time spent in each step
2 Wait time between each step
3
Pull request metrics – time to close, reviewers/approvals, comments and
size

16. Change lead time
What to measure?
1 Time spent in each step
2 Wait time between each step
3
Pull request metrics – time to close, reviewers/approvals, comments and
size

17. Change lead time
visualisations
35h
Average change
lead time
20h
Average
wait time
6h
Average PR
time to close
SeptAugJulJunMay
Hours
Average change
lead time by team

18. Wait Time vs %
resource busy
Wait Time = (% Busy)/(% Idle) Wait Time

19. Codebase health
What to measure?
1 Age of dependencies/libraries
2 Age of vulnerabilities/libraries with vulnerabilities
3 Complexity, duplications, test coverage etc…

20. Codebase health
What to measure?
1 Age of dependencies/libraries
2 Age of vulnerabilities/libraries with vulnerabilities
3 Complexity, duplications, test coverage etc…

21. Codebase health
What to measure?
1 Age of dependencies/libraries
2 Age of vulnerabilities/libraries with vulnerabilities
3 Complexity, duplications, test coverage etc…

22. Codebase
health
Dependent Library Age
Jackson
JSON
AWS SDK
Apache Commons
IO
Log4J
B
Overall
codebase health
3m
Average
dependency age
10
Known
vulnerabilities
Repository 1
Repository 2
Repository 3
Repository 4
Repository 5
Repository 6
B
A
D
F
A
A

23. Service health
What to measure?
1 Data stores and communication channels
2 Deployability
3 Alignment with architectural principals
4 Time since last deployment

24. Service health
What to measure?
1 Data stores and communication channels
2 Deployability
3 Alignment with architectural principals
4 Time since last deployment

25. Service health
What to measure?
1 Data stores and communication channels
2 Deployability
3 Alignment with architectural principals
4 Time since last deployment

26. Service health
What to measure?
1 Data stores and communication channels
2 Deployability
3 Alignment with architectural principals
4 Time since last deployment

27. Service Health
score card
Attribute Weight Score
TOTAL
Is HTTPS used for all
HTTP communication?
Is data encrypted at rest
Does this service handle more
than one concern?
Is this service stateless?
Can this service be deployed
without downtime / service
interruption?
Can this service be scaled
horizontally?
Is the data decoupled
from the applications?
How long since the service was
last deployed to production?
10 10
10 0
20 20
10 10
20 0
10 10
5 5
-0.1 -2
53
C
Overall Service
Health
Score
75 - 85
60 - 75
50 - 60
35 - 50
Rating
A
B
C
D

28. What else
to measure?
• Age and vulnerabilities in 3rd party software
• Platform utilisation
• Operational alerts per team or service
• Team health

29. Recap
Measure
deployments
• Deployments per
engineer
• Deployments duration
• Time of day
• Success/failure
Measure
change lead time
• Time spent in each step
• Wait time
• Pull request metrics
Codebase
health
• Age of dependencies
• Age of vulnerabilities
• Overall health rating
Service
health
• Data stores and
communication channels
• Deployability
• Alignment with architectural
principals
• Time since last deployment

30. Stay in touch!
linkedin.com/in/ben-mostafa
developers@messagemedia.com.au
developers.messagemedia.com/collaborate/slack

31. www.developers.messagemedia.com
Australia | New Zealand | United Kingdom | United States