The document discusses the 6 steps of DevOps: plan, build, test, release, deploy, and monitor. It explains that DevOps aims to enable teams to continuously push value through optimizing people, tools, and processes. Some benefits of DevOps include faster software releases, minimum risk and disruption during deployment, and improved cross-team collaboration and culture. It provides tips for making the cultural transition to DevOps such as starting with small experimental teams and expanding practices iteratively. It also outlines best practices like collaboration, feedback and monitoring, automation, and service virtualization to help ensure quality while moving faster.

1. DevOps: 6 Steps to Go Faster, Build
Better and Avoid Disaster

2. Page
Proprietary & Confidential
2
DevOps: Best Practices to Go Faster, but Avoid a Quality Disaster
Your Team Members / DevOps Stages
Aaron: Plan Ronan: Build Dermot: Test Joe: Release
Damien: Deploy Noel: Monitor

3. Today’s Agenda
• DevOps story:
• The World of DevOps
• 6 steps in DevOps
• Making the Cultural Transition to DevOps
• How to Deploy Quality Software, Faster with DevOps
• On your feetexercise
• Discuss findings and interesting takeaways
DevOps: Best Practices to Go Faster, but Avoid a Quality Disaster

4. Page
What is DevOps?
DevOps is a holistic culture of collaboration between
development and operations teams, achieved by
optimizing people, tools and processes.
4
Dev teams: Business stakeholders, product
managers, designers, developers and testers
Ops teams: Release engineers, network
specialists, systems engineers, operations and
security teams.
DevOps: Best Practices to Go Faster, but Avoid a Quality Disaster

5. Page
Proprietary & Confidential
DevOps enables teams to push value continuously
5
WaterfallAgile
Design Build Test Implement
DevOps
Sprint 1 Sprint 2 Sprint 3 Sprint 4
DevOps: Best Practices to Go Faster, but Avoid a Quality Disaster

6. Page
Proprietary & Confidential
Benefits of DevOps
Software delivery with
minimum risk and
disruption
6
Builds cross-team
collaboration and
culture
Faster software
releases and value
creation
DevOps: Best Practices to Go Faster, but Avoid a Quality Disaster

7. Page
Making the Cultural Transition into DevOps
7
DevOps: Best Practices to Go Faster, but Avoid a Quality Disaster

8. Page
Proprietary & Confidential
How to transition into DevOps
Studyyourorganization and
lookforareasofimprovement.
Measure currentperformance
andefficiency
Do your homework1
Holdcross-teambrainstorming
sessions
Sharepain-points andobjectives
topromoteunderstanding
Sharing is caring3
Studythechallenges and
benefits ofimplementing
DevOpsinexperimental teams
Retrospect5
ExplainthebenefitsofDevOps
Acknowledge thatteamshave
barriersincommunication and
conflicting priorities
Bridge the gap
2
Startwithsmallexperimental
groupsofpeople whoarecross-
functional andcollaborative
Measure theirperformance
Start small
4
Makeimprovements tothe
processandtryagain
ExpandDevOpspractices
outside smalltestgroups
Expand iteratively
6
8
DevOps: Best Practices to Go Faster, but Avoid a Quality Disaster

9. Page
Proprietary & Confidential
Common Pitfalls to Avoid when Moving to DevOps
Faster releases but
neglecting user value
9
Lack of optimum
toolchain
Different perceptions
among stakeholders
?
DevOps: Best Practices to Go Faster, but Avoid a Quality Disaster

10. Page
How to Deploy Quality Software, Faster with DevOps
10
DevOps: Best Practices to Go Faster, but Avoid a Quality Disaster

11. Page
Proprietary & Confidential
Best Practices to Ensure Quality while Moving Faster with DevOps
Collaboration
Feedback and Monitoring
Automation
Service Virtualization
11
DevOps: Best Practices to Go Faster, but Avoid a Quality Disaster

12. Page
Proprietary & Confidential
12
DevOps: Best Practices to Go Faster, but Avoid a Quality Disaster

13. Page
Proprietary & Confidential
13
DevOps: Best Practices to Go Faster, but Avoid a Quality Disaster
API Tests
CI Pipeline
Unit Tests Package
Deploy
Service
UI Tests
Tests
Deploy
Application
Jenkins listens to
GitHub for pull-
requests.
API is deployed in a
temporary container.
API tests are run.
Full application is
deployed. E2E tests
are run.
Application is
monitored in
production
API Layer UI Layer
DevOps at a glance
…

14. Page
Proprietary & Confidential
6 Steps to Go Faster, Build Better and Avoid Disaster Software
quality
14
DevOps: Best Practices to Go Faster, but Avoid a Quality Disaster
plan
Plan
build
Build
test
Test
release
Release
deploy
Deploy
monitor
Monitor

15. Page
Proprietary & Confidential
15
DevOps: Best Practices to Go Faster, but Avoid a Quality Disaster
How it was How it should be

16. Page
Proprietary & Confidential
Page
Let the discussions begin
16
DevOps: Best Practices to Go Faster, but Avoid a Quality Disaster

17. Thank you!