The Ultimate Guide on DevOps
                     Click to edit MasterT tithle esty leUltimate 
Guide on DevOps
1
CliIcnktr tood uecdtitio Mnaster title style
• The word DevOps is a combination of the terms 
development and operations, meant to represent a 
collaborative or shared approach to the tasks performed by 
a company's application development and IT operations 
teams.
2 2
Source: www.techtarget.com
CliHcokw to d eodeist  DMeavsOteprs  twitoler ks?tyle
• DevOps is a methodology meant to improve work 
throughout the software development lifecycle. You can 
visualize a DevOps process as an infinite loop, comprising 
these steps: plan, code, build, test, release, deploy, 
operate, monitor and -- through feedback -- plan, which 
resets the loop.
3 3
Source: www.techtarget.com
CliWckh atot  perdoibt lMemasst edro teistl eD esvtyOlpes solve?
• DevOps solves communication and priority problems 
between IT specializations. To build viable software, 
development teams must understand the production 
environment and test their code in realistic conditions. A 
traditional structure puts development and operations 
teams in silos. 
4 4
Source: www.techtarget.com
CliTchke t oe veodliutt Mioans toefr D teitvlOe pstsyle
• The concept of DevOps was then popularized with the book 
The Phoenix Project in 2013. The Phoenix Project uses a 
fictional narrative to illustrate endemic problems and help IT 
managers understand the concepts and benefits of 
collaboration and shared technologies.
5 5
Source: www.techtarget.com
CliDcekv tOop esd bite nMeafsitesr title style
• fewer silos and increased communications between IT 
groups;
• faster time to market for software;
• rapid improvement based on feedback;
• less downtime;
• improvement to the entire software delivery pipeline through 
builds, validations and deployment;
• less menial work, thanks to automation;
• streamlined development processes through increased 
responsibility and code ownership in development; and
• broader roles and skills.
6 6
Source: www.techtarget.com
CliDcekv tOop esd ciht aMllaesnteger stitle style
• organizational and IT departmental changes, including new 
skills and job roles
• expensive tools and platforms, including training and 
support to use them effectively
• development and IT tool proliferation
• unnecessary, fragile or unsafe automation
• scaling DevOps across multiple projects and teams
7 7
Source: www.techtarget.com
CliDcekv tOop esd tiot oMlsaster title style
• DevOps is a mindset, not a tool set. But it's hard to do 
anything in an IT team without the right tools. In general, 
DevOps practitioners rely on a CI/CD pipeline, containers 
and cloud hosting. Tools can be open source, proprietary or 
supported distributions of open source technology. 
8 8
Source: www.techtarget.com
CliDcekv tOop esd sikt iMllsaster title style
• DevOps is often said to be more of a philosophy or 
collaborative IT culture, rather than a strictly defined job 
description or skill set. Because the area is so broad, 
DevOps positions suit IT generalists better than specialists.
9 9
Source: www.techtarget.com
CliGcoka tlo o ef dDiet vMOapsster title style
• Improve deployment frequency
• Achieve faster time to market
• Lower failure rate of new releases
• Shorten lead time between fixes
• Improve mean time to recovery
1100
Source: www.techtarget.com
Click to edit Master title style
THANK YOU
11