2. Contents:
▰ Software Delivery
▰ DevOps Tool Chain
▰ DevOps Tools
▰ Need of DevOps
▰ DevOps Challenges
▰ Conclusion
▰ Other Top Trending
Technologies 2
▰ DevOps Overview
▰ What Actually DevOps is?
▰ CALMS
▰ Agile Approach
▰ Agile Vs DevOps
▰ Typical Deployment
Landscape
3. “DevOps is the practice of development and
operation engineers participating together in
the entire service lifecycle,
from design through the development
process to production support.
33
DevOps
4. What Actually is DevOps?
DevOps is a software
development methodology that
stresses communication,
collaboration, integration
between software developers,
testers and information
technology professional.
4
5. What Actually is DevOps?
DevOps is an approach based on agile and lean principles in which business owners,
development, operations, and quality assurance team collaborate to deliver software
in a continuous stable manner.
▰ DevOps is an environment that promotes cross practicality, shared business tasks
and belief
▰ DevOps is a movement that improves IT service delivery agility
▰ DevOps is a culture that promotes better working relationship within the company
▰ DevOps is a set of practices that provides rapid, reliable software delivery
5
6. DevOps is About CALMS
Culture
▰ People and process first
▰ If you don’t have culture, all automation attempts will be fruitless
▰ Culture of shared responsibility
Automation
▰ Automating Manual Tasks using tools which can only be achieved
after cultivating a proper work culture
▰ Team members seek out ways to automate as many tasks as
possible and are comfortable with the idea of continuous delivery
6
7. CALMS:
Lean
▰ Team members are able to visualize WIP, limit batch sizes and manage queue lengths
Measurement
▰ If you can’t measure, you can’t improve
▰ Measurement of everything it can as often as it can
▰ Performance metrics, process metrics, and even people metrics
Sharing
▰ Creating a culture where people share ideas and problems is critical
▰ This user-friendly communication channel encourages ongoing communication between
development and operations 7
8. The Agile Approach:
What is Agile Methodology
▰ Agile Methodology is practice which involves continuous iteration
of development and testing in the SDLC process.
▰ This software development methodology emphasizes on iterative,
incremental, and evolutionary development.
▰ Agile development process breaks the product into smaller pieces
and integrates them for final testing.
▰ It can be implemented in many ways, like scrum
8
9. Agile vs DevOps Approach:
▰ Agile addresses gaps in Customer and Developer communications
9
10. Agile vs DevOps Approach:
▰ DevOps addresses gaps in Development and IT Operations communications
10
11. Agile Vs DevOps
▰ Addressing the gaps between
Customer requirement and
Dev + Testing Team
▰ Cross Functional Teams to
design, develop and test
features and stories
prioritised by Customer
▰ Focuses more on functional
and non-functional
requirement.
▰ Addresses the gap between
Dev + Testing and Ops
▰ Automated release
management
▰ Focuses on functional and
non-functional plus operation
and business readiness
▰ Intensifies readiness and
automation
11
13. 13
Time to Delivery Internal software release once every 3-6 months Internal software release multiple
times a week
Quality and Testing Manual Testing of upto 50% of software releases
performed by large teams
Automated testing with more than
80% coverage requires limited
human intervention to validate
Software
Deployment
Manual Deployment of software can take multiple
individual steps; limited success
Fully automated deployment of
software; once click process can
launch multiple steps at a time
Monitoring and
Support
Reactive Software Monitoring issues, downtime
reported to users in hours, days
Proactive software health-
monitoring issues, downtime
reported to users in seconds,
preventive actions taken at defined
thresholds
Traditional Software Delivery VS DevOps Software Delivery
Software Delivery
21. When To Implement DevOps:
When To Adopt
▰ For E-commerce and
other web site
projects
▰ For Cloud Platforms
When Not to Adopt
▰ Mission critical
applications
▰ Ex: Banks, Power Systems
21
22. Coming From To
One of the Most Important Results of Implementing DevOps
22
Failure is not a cause for blame, it is a vehicle for change, learning,
and improvement.
23. Conclusion:
Technical Benefits:
➔ Continuous
software delivery
➔ Less complexity to
manage
➔ Faster resolution of
problems
Cultural Benefits:
➔ Happier, more
productive teams
➔ Higher employee
engagement
➔ Greater professional
development
opportunities
23
Business Benefits:
➔ Faster delivery of
features
➔ More stable operating
environments
➔ Improved communication
and collaboration
➔ More time to innovate
(rather than fix/maintain)
24. Other Trending Technologies in Market:
➔ Block Chain
➔ RPA
➔ AI
➔ IOT
➔ Cloud Computing
➔ Big Data
➔ Data Science
➔ AR and VR
24
25. References:
▰ DevOps - Wikipedia
▰ DevOps.com
▰ Guru99.com
▰ Atlassian.com
▰ DevOps White Paper - Happiest
Minds
▰ Architecting.co.uk
▰ Sei.cmu.edu
▰ Edureka - Youtube
25