<p>The types of numbers you're looking for might be hard to come across, because they're highly variable (even within one organization, it varies service-to-service and team-to-team, in my experience.) The <a href="https://landing.google.com/sre/workbook/toc/" rel="nofollow noreferrer">SRE Workbook</a> is now available for free, and includes two case studies (chapter 3) that might be helpful. Also, New Relic's <a href="https://newrelic.com/resource/site-reliability-engineering" rel="nofollow noreferrer">SRE eBook</a> does a really good job of summarizing SRE in a concise way.</p>

<p>Another way to approach this would be to try to use what you know about your service today to create a <a href="https://cloud.google.com/blog/products/gcp/know-thy-enemy-how-to-prioritize-and-communicate-risks-cre-life-lessons" rel="nofollow noreferrer">risk assessment</a> and estimate downtime you can prevent if you had SRE and dev support to eliminate those risks</p>

CC BY-SA 4.0
2019-02-12T16:56:52.197Z
Over time I understood that some decision makers will not realise risks after they happened. Therefore you need to make risk assessments and wait for things you predicted to happen or look for datapoints, e.g. to how many companies happened x&y that did not incorporated sre practices vs vice versa.
Grzegorz Wierzowiecki
CC BY-SA 4.0
2019-02-08T22:09:39.447Z
2019-02-08T22:09:39.447Z
Eric Harvieux
<p>I am operating in both DevOps and Site Reliability Engineering organisations across several companies.  I would say that SRE has the advantage of being far more concrete than DevOps.</p>

<ul>
<li><p><strong>DevOps</strong> emphasises principles and mindsets, for example, the three ways of DevOps: Systems Thinking, Amplification of Feedback Loops and a Culture of Continuous Experimentation and Learning.  DevOps more of an extension to Agile that a different operating model.</p></li>
<li><p><strong>Site Reliability Engineering</strong> emphasises the specific approaches, metrics and measures that Google (and others) apply to achieve a high level of service availability and confidence in the customer.  f.ex: The ratio of toil to improvements, quantitative risk analysis and mathematical approaches to SLIs and SLOs.</p></li>
</ul>

<p>Because <a href="https://www.youtube.com/watch?v=uTEL8Ff1Zvk" rel="nofollow noreferrer">SRE Implements DevOps</a> it's a little unfair to try and compare organisations who do one but don't do the other, so I would actually suggest that all of the content in <a href="https://www.amazon.co.uk/dp/B07B9F83WM" rel="nofollow noreferrer">Accelerate</a> can just as easily be applied to Site Reliability Engineering, thus if you need peer-reviewed data-driven analytics to start there. </p>

CC BY-SA 4.0
2019-10-17T14:15:58.027Z
2019-10-17T14:15:58.027Z
Richard Slater
<p>As there is no Site Reliability Engineering dedicated stackexchange, I found this to be closes one.</p>

<p>There are multiple great resources to use as inspiration for slidedeck about SRE principles [SRE slides].</p>

<p>Still I can't find : </p>

<ul>
<li>short</li>
<li>concise</li>
<li>examples</li>
<li>motivating spending resources to implement SRE in organisation.</li>
</ul>

<p>Most what I experienced in my professional life were highly confidential cases and numbers. I am concerned that most numbers that SREs know, are to remain "internal" to be presented internally within corporations.</p>

<p>However, maybe you know some study, (preferably set of) nice examples of post-morthems (even one by one is good),  from which we could make a strong arguments like "after introducing SRE model into organisation velocity of changes grown from n to m release pushes per x, with increase of availability by y and decrease of costs by z" (brainstorming) or other hard data points?</p>

<p>[SRE slides] - some examples:</p>

<ul>
<li><a href="https://www.slideshare.net/lschwartz925/site-reliability-engineering-an-enterprise-adoption-story-an-itsm-academy-webinar" rel="noreferrer">Site Reliability Engineering: An Enterprise Adoption Story (an ITSM Academy Webinar) by ITSM Academy, Inc.</a></li>
<li><a href="https://www.slideshare.net/GrierJohnson/sre-from-scratch" rel="noreferrer">SRE From Scratch by 
Grier Johnson, Platform Engineer at Square</a></li>
<li><a href="https://www.youtube.com/watch?v=Cxb7a8lTv8A" rel="noreferrer">GOTO 2017 • Site Reliability Engineering at Google • Christof Leng</a></li>
</ul>

<p>P.S. If this question could be rephrased to fit better into this site guidelines, please provide me a suggestion in comment and give me a change to improve. Otherwise, I will appreciate other better platforms (However e.g. reddit.com/r/sre did not make great impression to me)</p>

CC BY-SA 4.0
2018-09-21T01:40:14.417Z
[SRE Handbook](https://landing.google.com/sre/book/index.html) is a great read for a team trying to implement SRE practices.
user9921
CC BY-SA 4.0
2018-09-21T10:11:12.500Z
Chef.io has a bunch of resources, including 4 webminars about devops and speed which may inrerest you: https://www.chef.io/resources/ some customer stories like Rakuten could give you some insights also, I don't know a definitive hard rule guide that said
Tensibai
CC BY-SA 4.0
2018-09-26T01:49:15.360Z
The book.ACCELERATE (Forsgene, Gene) does same for DevOps but some datapoints might be compatible, like a service MTTR (mean time to recover)
Ta Mu
<sre>
Datapoints motivating introduction of SRE in organisation
Grzegorz Wierzowiecki
# Datapoints motivating introduction of SRE in organisation

(Asked by: username_0 on 2018-09-20)

As there is no Site Reliability Engineering dedicated stackexchange, I found this to be closes one.

There are multiple great resources to use as inspiration for slidedeck about SRE principles [SRE slides].

Still I can't find :

* short
* concise
* examples
* motivating spending resources to implement SRE in organisation.

Most what I experienced in my professional life were highly confidential cases and numbers. I am concerned that most numbers that SREs know, are to remain "internal" to be presented internally within corporations.

However, maybe you know some study, (preferably set of) nice examples of post-morthems (even one by one is good), from which we could make a strong arguments like "after introducing SRE model into organisation velocity of changes grown from n to m release pushes per x, with increase of availability by y and decrease of costs by z" (brainstorming) or other hard data points?

[SRE slides] - some examples:

* [Site Reliability Engineering: An Enterprise Adoption Story (an ITSM Academy Webinar) by ITSM Academy, Inc.](https://www.slideshare.net/lschwartz925/site-reliability-engineering-an-enterprise-adoption-story-an-itsm-academy-webinar)
* [SRE From Scratch by
  Grier Johnson, Platform Engineer at Square](https://www.slideshare.net/GrierJohnson/sre-from-scratch)
* [GOTO 2017 • Site Reliability Engineering at Google • Christof Leng](https://www.youtube.com/watch?v=Cxb7a8lTv8A)

P.S. If this question could be rephrased to fit better into this site guidelines, please provide me a suggestion in comment and give me a change to improve. Otherwise, I will appreciate other better platforms (However e.g. reddit.com/r/sre did not make great impression to me)

**Tags:** sre

> **Comments:**
> **username_1**: [SRE Handbook](https://landing.google.com/sre/book/index.html) is a great read for a team trying to implement SRE practices.  
> **username_2**: Chef.io has a bunch of resources, including 4 webminars about devops and speed which may inrerest you: https://www.chef.io/resources/ some customer stories like Rakuten could give you some insights also, I don't know a definitive hard rule guide that said  
> **username_3**: The book.ACCELERATE (Forsgene, Gene) does same for DevOps but some datapoints might be compatible, like a service MTTR (mean time to recover)  

---

## 2 answers

### Answer by username_4 on 2019-02-08. Score: 3

The types of numbers you're looking for might be hard to come across, because they're highly variable (even within one organization, it varies service-to-service and team-to-team, in my experience.) The [SRE Workbook](https://landing.google.com/sre/workbook/toc/) is now available for free, and includes two case studies (chapter 3) that might be helpful. Also, New Relic's [SRE eBook](https://newrelic.com/resource/site-reliability-engineering) does a really good job of summarizing SRE in a concise way.

Another way to approach this would be to try to use what you know about your service today to create a [risk assessment](https://cloud.google.com/blog/products/gcp/know-thy-enemy-how-to-prioritize-and-communicate-risks-cre-life-lessons) and estimate downtime you can prevent if you had SRE and dev support to eliminate those risks

> **Comments:**
> **username_0**: Over time I understood that some decision makers will not realise risks after they happened. Therefore you need to make risk assessments and wait for things you predicted to happen or look for datapoints, e.g. to how many companies happened x&y that did not incorporated sre practices vs vice versa.  

---

### Answer by username_5 on 2019-10-17. Score: 1

I am operating in both DevOps and Site Reliability Engineering organisations across several companies. I would say that SRE has the advantage of being far more concrete than DevOps.

* **DevOps** emphasises principles and mindsets, for example, the three ways of DevOps: Systems Thinking, Amplification of Feedback Loops and a Culture of Continuous Experimentation and Learning. DevOps more of an extension to Agile that a different operating model.
* **Site Reliability Engineering** emphasises the specific approaches, metrics and measures that Google (and others) apply to achieve a high level of service availability and confidence in the customer. f.ex: The ratio of toil to improvements, quantitative risk analysis and mathematical approaches to SLIs and SLOs.

Because [SRE Implements DevOps](https://www.youtube.com/watch?v=uTEL8Ff1Zvk) it's a little unfair to try and compare organisations who do one but don't do the other, so I would actually suggest that all of the content in [Accelerate](https://www.amazon.co.uk/dp/B07B9F83WM) can just as easily be applied to Site Reliability Engineering, thus if you need peer-reviewed data-driven analytics to start there.


---

