- The document provides a brief history of the State of DevOps report from 2012-2017 and introduces the authors of the report.
- It summarizes key findings from the 2017 report including that high-performing teams deploy code 46x more frequently and have 440x faster lead times than low performers. These teams also automate more tasks.
- The document states that loosely coupled architectures and teams best enable continuous delivery and that lean product management drives higher organizational performance. It encourages questions from the audience.
Advantages of Hiring UIUX Design Service Providers for Your Business
Key Findings from the 2017 State of DevOps Report 06.08.2017
1.
2. Agenda
• A brief history of SODOR
• Who took the survey
• Key findings
• Questions
3. About the authors
Dr. Nicole Forsgren
@nicolefv
Jez Humble
@jezhumble
Gene Kim
@realgenekim
Nigel Kersten
@nigelkersten
Alanna Brown
@alannapb
4. A brief history of the State of DevOps Report
2012:
What is devops?
2013:
DevOps adoption
is accelerating.
2014:
Holy cow!
DevOps works!
2015:
IT goes lean.
2016:
Shifting left.
2017:
DevOps works for
all organizations.
8. Transformational leaders share
five common characteristics that
significantly shape an organization's
culture and practices, leading to
high performance.
9. By 2020, half of the CIOs
who have not transformed
their teams' capabilities will be
displaced from their organizations’
digital leadership teams.
13. More frequent
Code deployments
46x
That’s the difference between multiple
times per day and once a week or less.
Faster lead time from
commit to deploy
440x
That’s the difference between less than
an hour and more than a week.
14. 96xfaster mean time to
recover from downtime
That means high performers recover in
less than an hour instead of several days.
5xas likely that
changes will fail
That means high performers’ changes fail 7.5%
of the time instead of 38.5%.
20. Overcoming the J-curve
20
Low speed
Low stability
Low innovation
Low retention
High speed
High stability
High innovation
High retention
Early wins
The hard road
Real success
22. High performing organizations are
twice as likely to achieve or exceed goals
Commercial Goals
● Productivity
● Profitability
● Market Share
● # of customers
Non-commercial Goals
● Quantity of products or services
● Operating efficiency
● Customer satisfaction
● Quality of products or
services provided
● Achieving organizational
and mission goals
24. High performing organizations are
twice as likely to achieve or exceed goals
● Can do testing without requiring integrated environment
● Application can be deployed / released independently of
other apps and services they interact with
● Teams make their own tool decisions
● Teams are empowered to test, deploy, and change
systems independently
● Delivery requires dedicated testing environment and
lengthy integration testing
● Applications are monolithic and must be built and
deployed as a single unit
● Teams forced to use tools mandated by central group
● Teams are constrained by other teams
25. Architectural outcomes: can my team…
25
• …make large scale changes to the design of its system without the
permission of someone outside the team, or depending on other teams?
• ...complete its work without fine-grained communication and coordination
with people outside the team?
• ...deploy and release its product or service on demand, independently of
other services the product or service depends upon?
• ...do most of its testing on demand, without requiring an integrated test
environment?
• ...perform deployments during normal business hours with negligible
downtime?
26. Conway’s Law
“organizations which design systems …
are constrained to produce designs
which are copies of the communication
structures of these organizations”
28. Lean Product Management Practices
Working in small batches
Making the flow of work visible through the process
Gathering, broadcasting and implementing customer feedback
Ability of teams to try out new ideas and create
and update specifications during the development process
30. Get your copy of the
2017 State of DevOps Report
puppet.com/state-of-devops-report
Notes de l'éditeur
High performing IT organizations are still deploying more frequently with fewer failures.
- High performers deploy 46x (compared to 200x in 2016) more frequently than low performers. This is the difference between being able to deploy on demand multiple times a day and only being able to deploy a one or two times a month.
- High performers also have 440x (compared to 2,555x faster in 2016) lead times. They can push a change to production in less than an hour versus once every couple of months.
- They also recover from failures 24x faster. This is the difference between an hour and a day, which is significant when you factor in the average cost of downtime per hour.
- High performing organizations also have 1/5 the change failure rate (or 5x lower change failure rate).
Takeway: High performers are maximizing throughput while maintaining the highest levels of stability. This means they are able to get new features and bug fixes to market faster, get customer feedback, and iterate more rapidly.
Low performers have increased their throughput, compared to 2016 results, and are deploy faster and more frequently, but they’re still doing poorly in terms of stability. We speculate that this is due to low-performing teams are optimizing for speed, but not investing enough in building quality into the process, which takes time.
The result is larger failures that take more time to restore service. High performers understand that they don’t have to trade speed for stability or vice versa, because by building quality in, they get both.
When we compared high performers to low performers, we found that high performers have the lowest amounts of manual work at statistically significant levels.
Only 28% of their config management work is manual compared to 46% for low performers
35% of testing is done manually compared to 49%
26% of deployments compared to 43%
and everyone sucks at change approval, but high performers are still better with 48% manual compared to 59%
Extra stats:
33 percent more of their configuration management is automated
27 percent more of their testing is automated
30 percent more of their deployments is automated
27 percent more of their change approval processes automated