Skip to main content

DevOps & the Top 5 Predictors of IT Performance


DevOps is here and it seems to be what everyone in ITSM is buzzing about. So what are the goals and how do we know it’s not just the next hot kitchen color for this year?  DevOps is a cultural and professional movement that stresses communication, collaboration and integration between software developers and IT operations professionals while leveraging agile, lean and traditional ITSM practices.

Stakeholders on the development side will include, but not be limited to, all of the people involved in developing software products and services.  On the operations side it will include, but not be limited to, all of the people involved in delivering and managing those software products and services and the underlying IT infrastructure on which it is being delivered.

 The goals are to better align IT responsiveness to business needs, smaller more frequent releases, reduce risk, increase flow, improve quality and reduce time to market. These can only be accomplished by understanding the entire value stream, including the lead times and cycle times of the different areas that make up your value stream.

Let's take a look at the top 5 predictors of IT performance and see how engaging DevOps practices enhances our ability to become high performing teams.
  1. The peer review change approval process provides enhanced and effective communication.  When technical teams hold themselves accountable for the quality of their code through peer review their performance increases resulting in 200 more times frequent code deployments. (1) Allows for an on demand deployment (multiple, daily releases) structure.
  2. Version control for all production artifacts. This provides a single source of truth for all changes. An integrated and automated tool chain along with practices like continuous integration and we have a 3 times lower failure rate. (2)
  3. Proactive monitoring enables teams to diagnose and solve problems faster and have a higher degree of accountability.  Tie that in with a single source of truth and that results in 24 times faster (MTTR) Mean Time to Recover. (3)
  4. High trust organizational cultures allow for experimentation and learning, allowing people to take intelligent risks. Having this culture promotes the idea that repetition and practice is the prerequisite to mastery.  Organizations with high NPS (Net Promoter Score) have shown much higher levels of employee retention and are 2.2 times more likely to recommend their company as a good place to work. (4)
  5. A win-win relationship between Dev and Ops.  It’s not Dev vs Ops, it’s Dev and Ops. Shifting left is about building quality into the software development process. When you shift left fewer things break in production because issues are detected and resolved earlier. By building quality into the software development cycle, high performing teams spend less time on unplanned work. We also found that they spend less time remediating issues and spend more time on new, value-add work.
***1,2,3,4 From 2016 State of DevOps Report PuppetLabs

For more information on DevOps Training: http://www.itsmacademy.com/dofnd/

Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you.

Roles and Responsibilities:
Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance.Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…