20
A 5-min Ignite talk about how DevOps beats Traditional IT Ops, every time. Oliver White (@theotown) Head of Rebel Labs, ZeroTurnaround DevOps Productivity Survey 2013

DevOps Productivity Report 2013 ignite talk

Embed Size (px)

DESCRIPTION

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/

Citation preview

Page 1: DevOps Productivity Report 2013 ignite talk

A 5-min Ignite talk about how DevOps beats Traditional IT Ops, every time.

Oliver White (@theotown)Head of Rebel Labs, ZeroTurnaround

DevOps Productivity Survey 2013

Page 2: DevOps Productivity Report 2013 ignite talk

Reminder: Why we want DevOps

● Traditionally siloed team structures don’t scale

● Opposing philosophies (Devs <3 change, Ops <3 stability)

● Continuously evolving technologies & needs require more flexibility

How do DevOps teams spend their time each week, compared to Traditional IT Ops teams?

Page 3: DevOps Productivity Report 2013 ignite talk

DevOps vs. Traditional IT Ops: Overall work week

Page 4: DevOps Productivity Report 2013 ignite talk

DevOps vs. Traditional IT Ops: Infrastructure improvements

What they're doing: testing processes and recovery plans and making sure these things work

DevOps spends 33% more time improving infrastructure against failures.

Page 5: DevOps Productivity Report 2013 ignite talk

DevOps vs. Traditional IT Ops:Handling Support

What they're doing: Handling support cases for operations infrastructure - i.e. when things go wrong

Traditional IT Ops require nearly 60% more time per week to handle support cases.

Page 6: DevOps Productivity Report 2013 ignite talk

DevOps vs. Traditional IT Ops:Firefighting

What they're doing: dropping everything to recover from failures or fix something urgently.

DevOps spends about 21% less time putting out fires on a weekly basis.

Page 7: DevOps Productivity Report 2013 ignite talk

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, and they even spend 15% more time on self-improvement (education, training).

Page 8: DevOps Productivity Report 2013 ignite talk

What about failures and recoveries?

● Average team has 2 app failures per month

● Recovery time is >30min for over 50% of all respondents.

Page 9: DevOps Productivity Report 2013 ignite talk

DevOps vs. Traditional IT Ops:Recovery times

Page 10: DevOps Productivity Report 2013 ignite talk

DevOps vs. Traditional IT Ops:Recovery times

● Traditional IT Ops teams are almost 2x more likely to require 60+ minutes to recover

● Recoveries in < 30min are 33% more likely for DevOps teams than traditional IT Ops

Page 11: DevOps Productivity Report 2013 ignite talk

Ok ok, so DevOps recover faster....

But what about releasing software?

Surely DevOps can't be THAT much better?

Wrong.

Page 12: DevOps Productivity Report 2013 ignite talk

Boom!

DevOps teams need less than HALF THE TIME to release an application version (36.3 min vs. 85.1 min).

Page 13: DevOps Productivity Report 2013 ignite talk

Quick summary so far...

● DevOps spends more time on improving things and less time fixing things

● DevOps recovers from failures faster

● DevOps releases apps more than twice as fast

Hmm, maybe it's in the tools they are using?

Page 14: DevOps Productivity Report 2013 ignite talk

Top tools and technologies used by DevOps and IT Ops teams

Page 15: DevOps Productivity Report 2013 ignite talk

Let's ask the audience

Page 16: DevOps Productivity Report 2013 ignite talk

Popular infrastructure config tools

Page 17: DevOps Productivity Report 2013 ignite talk

Popular Test Automation tools

Page 18: DevOps Productivity Report 2013 ignite talk

Popular Monitoring tools

Page 19: DevOps Productivity Report 2013 ignite talk

DevOps clearly wins, but still isn't perfect (hey!)

● Most app failures still occur due to software quality or lack of automation.

● Most teams have < 10% of their infrastructure configured with code (i.e. using Puppet, Chef)

● Most teams have < 10% of their smoke tests automated

● Most teams don't test their recovery processes

Page 20: DevOps Productivity Report 2013 ignite talk

Thanks for your attention!

Twitter: @Rebel_LabsEmail: [email protected]: http://zeroturnaround.com/rebellabs

Psst: For the full report in pdf, give us a business card or your details and we'll send it to you