Leveraging Failure to Succeed in DevOps

1
Refer to document REF-00897 Lenovo Documents Library (LDL) The online version is the master 55 total slides2018 - Lenovo Confidential
Identifying and Learning from
Failures – Key to DevOps Success
Steve Brown, Director, WW DevOps Practice | July 11, 2018
Lenovo 2018. All Rights Reserved. devops@lenovo.com

2
What is DevOps?
DEV
Source: Wikipedia 2016
IT Ops
QA
DevOps

3
The DevOps Journey
• DevOps is a journey toward continuous learning in the context of improving
IT Performance.
• While every organization has a unique path and journey, the “patterns” are
well-known.
• The pattern is repeated cycles of small improvement projects, followed by
the ability to decide what the next best improvement to make is.
• Assess  Improve  Re-Evaluate – 3-Step Cycle

42018 - Lenovo Confidential
Key Points on DevOps…
• DevOps has roots in Agile – shorter development cycles, frequent feedback loops guide you quickly,
toward product delivery that is more aligned with customer needs.
• Combination of cultural philosophies, practices and tools that increases an organization’s ability to
deliver applications and services at high velocity.
• Emphasizes collaboration, risk-taking, metrics and process flexibility to enable continuous and rapid
improvement.
• Speed enables organizations to better serve their customers and compete more effectively in the
“Applications Economy”.
devops@lenovo.comLenovo 2018. All Rights Reserved.

5
Principle Failures of DevOps Adoption…
• “Failure to view the IT organization as a strategic profit center, and instead viewing it
as a cost center.”
• “Believing that there is a difference between "IT" and "The Business."
• Attempting a Digital Transformation that involves only some of the functions and
departments in the organization.”
• “Viewing Digital Transformation as anything less than inculcating an organizational
of continuous learning.”
-- Principal Consultant, DevOps Industry Leader

6
Turn Failures Into Success…
• DevOps is typically perceived as a way to avoid failure; however, failures are steps in the
right direction.
• Learning from failures and turning the DevOps practice into one that will lead you toward
even greater success – better, faster.
• Don’t Beat Them! -- Reward employees for taking risks and failures – leads to a culture of
innovation and job satisfaction.
• Feedback Loops – Learn from actions through customer feedback, measure what went
right and what can be improved (internal / external customers).
• Be Data-Driven -- Tracking and monitor progress of failures in processes and share data
with Lines-of-Businesses. Individual contributors need to see their data to learn, improve.

7
Leveraging Data…
• Metrics and Monitoring -- Measure the right information and manage the DevOps operation
to continuously keep the key performance indicators in the right balance.
• Faster development and deployment of software is great, but the real value of DevOps is
in delivering high-quality software, repetition and continuous improvement from failure
metrics.
• Continually improving the flow of work through development and deployment processes,
leveraging data from short feedback loops to make iterative improvements, creating and
deploying high-quality software.
• Data helps elevate job satisfaction and reduce employee burnout.
• Data fosters a culture of collaboration and support toward the organizational goals. Data
helps to remove emotion and cultural silos decision-making processes

8
Key Metrics to Track
• Lead time: For the primary application or service you work on, how long it takes to go from
code commit to code successfully running in production or in a releasable state.
• Deploy frequency: For the primary application or service you work on, how often code is
deployed.
• Mean time to restore (MTTR): For the primary application or service you work on how long
it generally takes to restore service when a service incident occurs (e.g. unplanned outage,
service impairment).
• Change fail percentage: For the primary application or service you work on, the percentage
of changes that result in degraded service or subsequently require remediation (e.g., lead to
service impairment, service outage, require a hotfix, rollback, fix forward, patch).
Also… deployment success rate, app error rates, incident severity, outstanding bugs

Visualize, Record, Analyze – Within All Processes…

DATA – Design, Code, Test, Deploy
Visualize, Record, Analyze – Within All Processes…

Leveraging Failure to Succeed in DevOps

More Related Content

What's hot

Similar to Leveraging Failure to Succeed in DevOps

Recently uploaded

Leveraging Failure to Succeed in DevOps