DevOps Productivity Report 2013 ignite talk
Upcoming SlideShare
Loading in...5
×
 

DevOps Productivity Report 2013 ignite talk

on

  • 2,304 views

The results from Rebel Labs "IT Ops and DevOps Productivity Report 2013", the full version of which can be found here: http://zeroturnaround.com/rebellabs/ops/it-ops-devops-productivity-report-2013/

The results from Rebel Labs "IT Ops and DevOps Productivity Report 2013", the full version of which can be found here: http://zeroturnaround.com/rebellabs/ops/it-ops-devops-productivity-report-2013/

Statistics

Views

Total Views
2,304
Views on SlideShare
1,457
Embed Views
847

Actions

Likes
2
Downloads
29
Comments
0

4 Embeds 847

http://zeroturnaround.com 826
http://dromologue.com 18
http://local.zeroturnaround.com 2
http://accessibility_checker.siteimprove.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

DevOps Productivity Report 2013 ignite talk DevOps Productivity Report 2013 ignite talk Presentation Transcript

  • A 5-min Ignite talk about how DevOpsbeats Traditional IT Ops, every time.Oliver White (@theotown)Head of Rebel Labs, ZeroTurnaroundDevOps ProductivitySurvey 2013
  • Reminder: Why we want DevOps● Traditionally siloed team structures don’t scale● Opposing philosophies (Devs <3 change, Ops <3stability)● Continuously evolving technologies & needs requiremore flexibilityHow do DevOps teams spend their time eachweek, compared to Traditional IT Ops teams?
  • DevOps vs. Traditional IT Ops:Overall work week
  • DevOps vs. Traditional IT Ops:Infrastructure improvementsWhat theyre doing: testing processes and recoveryplans and making sure these things workDevOps spends 33% more time improving infrastructureagainst failures.
  • DevOps vs. Traditional IT Ops:Handling SupportWhat theyre doing: Handling support cases foroperations infrastructure - i.e. when things go wrongTraditional IT Ops require nearly 60% more time per weekto handle support cases.
  • DevOps vs. Traditional IT Ops:FirefightingWhat theyre doing: dropping everything to recoverfrom failures or fix something urgently.DevOps spends about 21% less time putting out fires on aweekly basis.
  • DevOps wins!● 21% less time putting out fires● 37% less time handling support cases.● With that extra time, DevOps spends 33%more time improving infrastructure, andthey even spend 15% more time on self-improvement (education, training).
  • What about failures and recoveries?● Average team has 2 app failures permonth● Recovery time is >30min for over 50% ofall respondents.
  • DevOps vs. Traditional IT Ops:Recovery times
  • DevOps vs. Traditional IT Ops:Recovery times● Traditional IT Ops teams are almost 2xmore likely to require 60+ minutes torecover● Recoveries in < 30min are 33% more likelyfor DevOps teams than traditional IT Ops
  • Ok ok, so DevOps recover faster....But what about releasing software?Surely DevOps cant be THAT muchbetter?Wrong.
  • Boom!DevOps teams need less than HALF THETIME to release an application version (36.3min vs. 85.1 min).
  • Quick summary so far...● DevOps spends more time on improvingthings and less time fixing things● DevOps recovers from failures faster● DevOps releases apps more than twice asfastHmm, maybe its in the tools they are using?
  • Top tools and technologies used byDevOps and IT Ops teams
  • Lets ask the audience
  • Popular infrastructure config tools
  • Popular Test Automation tools
  • Popular Monitoring tools
  • DevOps clearly wins, but still isntperfect (hey!)● Most app failures still occur due to software qualityor lack of automation.● Most teams have < 10% of their infrastructureconfigured with code (i.e. using Puppet, Chef)● Most teams have < 10% of their smoke testsautomated● Most teams dont test their recovery processes
  • Thanks for your attention!Twitter: @Rebel_LabsEmail: labs@zeroturnaround.comWeb: http://zeroturnaround.com/rebellabsPsst: For the full report in pdf, give us a businesscard or your details and well send it to you