The Seven Deadly Sins of DevOps

7 deadly sins of devops

What to avoid when you start DevOps While there are many ways to do DevOps correctly, there are specific cardinal sins that will put you afoul of the Church of DevOps. From lacking an incident management tool to handle critical alerts to treating DevOps as a job title, there are many ways for you to hurt your status as an A-class DevOps shop. In order to achieve excellence in DevOps, it is key for executives to avoid committing the cardinal sins of DevOps that are discussed below. DevOps sin 1: You treat DevOps as a title, not a philosophy In speaking to directors of engineering at numerous companies, I have heard the phrase: ‘if you have Devops in your title, you’re doing it wrong’. The point of this statement is that DevOps is a philosophy, not a title. You shouldn’t assume that you can simply put the word ‘DevOps’ in someone’s title and get anywhere […] Read more »

MTTR by the Numbers

How MTTR is key to effective business

Ignoring MTTR can cost you millions Peter Drucker was famous for saying that “If you can’t measure it, you can’t improve it.” That’s why knowing your MTTR (mean time to resolution) is so important. If you don’t know how long it takes for you to fix issues, you cannot improve on that time. Effectively, MTTR is an important shorthand for your team to know how well they are doing in acknowledging and responding to software, hardware or deployment failures. Here are 3 key ways your team can improve their MTTR: Identifying the root cause is usually the biggest cause of MTTR variability and the one that has the highest cost associated with it. Ensure that information goes to the right person.  When a monitoring system detects an issue and sends an email, use OnPage to make sure that the correct engineer is alerted. Have escalations enabled so that engineers can reach […] Read more »

What you need to know about MTTR and why IT MaTTeRs

MTTR3

What all engineering teams should know about MTTR In the IT world, performance is everything. So when technology fails, your first thought is how to utilize incident management knowledge to repair the situation and minimize downtime. As both a manager and an engineer, you need to minimize your MTTR –Mean Time To Resolution- in order to comply with your SLAs – service level agreements – and keep your group at the top of its game.  This article will highlight the issues impeding effective MTTR management and offer insights on how to improve use of MTTR as a metric. Who cares about MTTR I have put the importance of MTTR out there and have not defined to whom in particular the metric is important. But the truth is that just about everyone in engineering uses MTTR to measure how long it takes their teams to resolve an incident after it has […] Read more »