Skip to main content

DevOps – IT and Business Performance


The relationship of IT Performance on Business Performance is becoming more evident today as service providers strive to meet the dynamic rate of change that is required to meet business requirements.  It is unfortunate that all too often the evidence for the lack of IT performance is brought to the forefront because processes break down, cost overruns occur, and business outcomes suffer.  When the flow of work is broken the service provider is not enabled to provision service at the rate of demand that is required and the cost of provisioning tends to soar.

When we look at the lifecycle for the deployment of a new or changed service we recognize that there are many roles, functions and activities that a service provider must manage and control.  When the development activities are silo’d from deployment and operational activities the value stream tends to break down and IT staff suffer.   This breakdown often results in frustrated staff that feel that they are not enable for success.  Capability for quality and efficiency is impeded.  Performance suffers and the competitive edge is not there.   DevOps is a cultural and professional movement that stresses communication, collaboration and most importantly integration between software developers and IT operation professionals.

Strong IT Performance Is Indeed A Competitive Advantage. 
Those organizations who recognize this and invest in strategies to increase it are those that can turn on dime and adapt to changes in legislation and market but more importantly are enabled to change when needed.  When development and delivery cycles are operating smoothly these high performing organizations can not only move but can efficiently change and move fast to meet market demands.  
The cultural practices and norms found in high trust organizations are also at the heart of DevOps, which helps to explain why DevOps practices correlate so strongly with high organizational performance. http://www.itsmacademy.com/Detail.bok?no=148



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…