Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

6.
Lots of changes, not deployed quickly enough
Ops, QA, Testing, Support not aligned with development
Deployment failures have risk of downtime
Development and ops must work together
What about IT Operations?
Today’s situation

7.
IT
Challenges
Visibility
Continuing pressure to improve
relevance of services.
Balance
IT must balance the rate of change
with stability.
Pressure
Scattered data or lack of data at all
limits incident and problem
understanding.

14.
Enabling the business and their customers by providing more
reliable services. When there’s an interruption, they’re able to
recover faster and minimize impact to the business.
High-performing IT organizations are

16.
What is
DevOps?
DevOps is a movement that
advocates a collaborative working
relationship between development
and IT operations.

17.
Development Operations
Everyone involved in developing
software products and services.
Everyone involved in delivering,
managing and supporting the
products and services.
Agile working relationship

18.
Where did DevOps come from?
•Processes in place today aren’t meeting business needs.
•Response to bureaucratic processes

30.
MTSR
• Mean-time-to-restore
• Did it increase or decrease?
Metrics
MTTR
• Mean-time-to-repair
• Did it increase or decrease?
Repetitive issues
• Did it increase or decrease?
SLAs/OLAs
• Service level agreements and
operational level agreements
• What is the impact of deployments
to achievements of service level
targets?
Cost per incident
Total cost of support
Cost of downtime