The document outlines five key ingredients for a successful DevOps transformation: systems thinking, collaboration, visualizing work-in-progress, source control, and adopting software-defined practices. It emphasizes the importance of continuous delivery, team collaboration, and visibility in the workflow to enhance efficiency and resilience in software development. The content features insights from industry experts and practical tools, such as Kanban boards and Azure templates.

1. www.devopsguys.com | Phone: 0800 368 7378 | e-mail: team@devopsguys.com | 2017
Start DevOps with Github and Azure
5 Key ingredients to your DevOps Transformation

2. 2
Agenda
•Getting Started with
DevOps
– Steve Thair, CTO, DevOpsGuys
•GitHub and Azure
– Alain Hélaïli, GitHub
•Q&A

3. DevOps in 6 slides in 3 minutes
Just so we’re all on the same page about this DevOps
thing…
Start the clock!

4. 4
“A set of patterns, practices and
behaviours that are correlated with
high-performing IT teams.”
DevOps – Defined #1

5. 5
DevOps = Continuous Delivery + Operability
Agile Software
Development + Continuous
Integration +
Test Automation +
Release Automation
= Continuous Delivery
DevOps = Agile
++
OPERABILITYScalability
Deployability
Resilience
Monitoring Alerting
Disaster Recovery
Supportability
Maintainability
+

6. 6
Continuous Delivery
“Our highest priority is to satisfy the customer through
early and continuous delivery of valuable software”

7. 7
The DevOps “CALMS” model
• Culture
• Automation
• Lean
• Measurement
• Sharing

8. 8

9. 9
Multi-Disciplinary Delivery Teams

10. Key Ingredient #1
“Systems Thinking” Mindset

11. 11
Gene Kim’s “3 Ways” of DevOps

12. 12
The
Business
I.T.

13. 13
Dev Ops

14. 14
Systems Thinking
Society
Customer
Business
I.T.
Dev
Ops

15. 15
Business
Department
Team
You
Values
Policies
Procedures
Behaviours
Culture
“Thewaythingsaredonearoundhere”

16. 16
This isn’t an easy Transformation…
From… Key Success Factor To…
Command & Control Management Style Autonomous
Conservative Attitude to Change Experimental
Silo Organisation Structure Collaborative
Project-focussed Delivery Focus Product-centric
Waterfall Delivery Model Iterative (Agile)
Large (Huge) Batch size Smallest possible
Monolithic Systems Architecture Loosely coupled
Proprietary Technology Open (Source)
Manual Processes Automated

17. Key Ingredient #2
Collaboration

18. 18
https://s-media-cache-

19. 19
Defining Devops II
“I’ll tell you EXACTLY what DevOps means.
DevOps means giving a sh*t about your job
enough to not pass the buck.
DevOps means giving a sh*t about your job
enough to want to learn all the parts and not just
your little world.
Developers need to understand infrastructure.
Operations people need to understand code.
- John E. Vincent (@Lusis)
http://blog.lusis.org/blog/2013/06/04/devops-the-title-match/

20. 20
What kind of Silo do you have?

21. 21
Dev Ops
M.A.D.

22. 22

23. 23
PullRequestsarea
greatplacetostart
collaborating!

24. Key Ingredient #3
Ability to visualise Work-In-Progress (WIP)

25. 25
#MakeWorkVisible

26. 26
https://communitiesinnature.wordpress.com/2012/04/10/our-gantt-chart-is-finished-westonbirt-arboretums-hidden-voices-project/
A Gannt Chart
is NOT
visualising
work

27. 27
A KANBAN
Board *IS*
Visualising Work

28. 28
To Do
Some Stuff
to Do
Ready
Stuff Ready
to Action
In-
Progress
This is what
I’m doing
right now!
Done
Done and
signed off by
everyone.
“Done Done.”
Sticky Label Design "© Copyright Showeet.com"
And it’ll be
done when it’s
done…
So stop
bugging me for
status updates
and go check
the board… A Kanban Board
without WIP limits
is… just a board!
3 5 3

29. Key Ingredient #4
Source control (everything)

30. 30
First Rule of Source Control
If it’s not in Source
Control it doesn’t Exist

31. 31
Second Rule of Source Control
All you need to rebuild your
environment is:
1. Your Git Repo
2. Your Password Vault
3. Your Data Replica/Backup
4. A Credit Card…

33. Key Ingredient #5
Software-Defined <Everything>

34. 34
SDx
•Software-Defined Instructure (SDI)
•Software-Defined Networking (SDN)
•Software-Defined Storage (SDS)
•Software-Defined Data Centre (SDDC)
•Use Hyper-Scale Public Cloud E.g. Azure

35. 35
Azure Quick Start Templates
http://bit.ly/AzureButton
http://bit.ly/AzureDCOSGit

36. 36
Passing a JSON file (ARM Template) to Azure
• https://portal.azure.com/#create/M
icrosoft.Template/uri/https%3A%2
F%2Fraw.githubusercontent.com%
2FAzure%2Fazure-quickstart-
templates%2Fmaster%2F101-acs-
dcos%2Fazuredeploy.json
• 148 lines
• Creating Azure Container Service
(ACS) resource
"resources": [
{
"apiVersion": "2016-03-30",
"type":
"Microsoft.ContainerService/containerServices"
,
"location":
"[resourceGroup().location]",
"name":"[concat('containerservice-
',resourceGroup().name)]",
"properties": {
"orchestratorProfile": {
"orchestratorType":
"[variables('orchestratorType')]"
},
"masterProfile": {
"count":
"[variables('masterCount')]",
"dnsPrefix":
"[variables('mastersEndpointDNSNamePrefix')]"
},
"agentPoolProfiles": [

37. 37
Summary – 5 key ingredients
1.Systems Thinking
2.Collaboration
3.Visualise WIP
4.Source Control
5.Software-Defined <Everything>

38. Questions?

39. DevOps Solutions
DevOps Coaching
Workshops & Training
DevOps Engineering
Application Lifecyle
Automation
DevOps Consultancy
DevOps, Agile & Cloud
Strategy
ccelerateducate ransform