DevOps Productivity Report 2013 ignite talk


Published on

The results from Rebel Labs "IT Ops and DevOps Productivity Report 2013", the full version of which can be found here:

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

DevOps Productivity Report 2013 ignite talk

  1. 1. A 5-min Ignite talk about how DevOpsbeats Traditional IT Ops, every time.Oliver White (@theotown)Head of Rebel Labs, ZeroTurnaroundDevOps ProductivitySurvey 2013
  2. 2. 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?
  3. 3. DevOps vs. Traditional IT Ops:Overall work week
  4. 4. 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.
  5. 5. 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.
  6. 6. 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.
  7. 7. 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).
  8. 8. What about failures and recoveries?● Average team has 2 app failures permonth● Recovery time is >30min for over 50% ofall respondents.
  9. 9. DevOps vs. Traditional IT Ops:Recovery times
  10. 10. 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
  11. 11. Ok ok, so DevOps recover faster....But what about releasing software?Surely DevOps cant be THAT muchbetter?Wrong.
  12. 12. Boom!DevOps teams need less than HALF THETIME to release an application version (36.3min vs. 85.1 min).
  13. 13. 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?
  14. 14. Top tools and technologies used byDevOps and IT Ops teams
  15. 15. Lets ask the audience
  16. 16. Popular infrastructure config tools
  17. 17. Popular Test Automation tools
  18. 18. Popular Monitoring tools
  19. 19. 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
  20. 20. Thanks for your attention!Twitter: @Rebel_LabsEmail: labs@zeroturnaround.comWeb: For the full report in pdf, give us a businesscard or your details and well send it to you