DevOps Methodology

1. DevOp
s
A COMPOUND OF DEVELOPMENT (DEV) AND OPERATIONS (OPS), DEVOPS IS
THE UNION OF PEOPLE, PROCESS, AND TECHNOLOGY TO CONTINUALLY
PROVIDE VALUE TO CUSTOMERS.

2. • Collaboration and co-ordination
across teams
• Ability to better respond to
customer needs
• Increase confidence in the
applications they build
• Achieve business goals faster
• Accelerating time to market
• Adapting to the market and
competition
• Maintaining system stability and
reliability
• Improving the mean time to
recovery
Why DevOps…..??

4. Plan
Ideate, define, and
describe features and
capabilities of the
applications
 Creating
backlogs
 Tracking bugs
 Managing agile
software
development
with Scrum
 Using Kanban
boards
 Visualizing
progress with
dashboards
Deliver
Deploying
applications and
configuring the
fully governed
foundational
infrastructure
 Defining
release
management
process with
clear approval
stages.
 Setting
automated
gates that
move
applications
between
stages
Develop
Writing, testing
reviewing, and
the integration of
code
 Tracking
using
productive
tools
 Automate
mundane
and manual
steps
 Iterate in
small
increments
Continuous
integration.
Operate
maintaining,
monitoring, and
troubleshooting
applications in
production
environments.
 Identify issues
before they
affect the
customer
experience
 Mitigate issues
quickly when
they do occur.
How to we adapt DevOps

5. Collaboration, visibility, and alignment
• Visibility across teams
• Alignment of goals
Shifts in scope and accountability
• Collective responsibility across teams
Shorter release cycles
• planning and risk management is easier
• progress is incremental
• adapt and react to evolving customer needs and competitive pressure.
Continuous learning
• Growth mindset
• Continuous improvement
• Increased customer satisfaction
• Market adaptability.
What is in it for us..??

6. How do we go about
implementing this….?