Skip to main content

Xtreme Velocity - Accelerating Change Management

Although Agile, DevOps and automation for Continuous Delivery (CD) techniques are on the rise, service providers are still at risk for not having the necessary velocity to meet demand.  In the same way that we recognize that we can NOT silo our IT teams, we must also recognize that as providers of services we must not silo our processes. ITSM processes, including Event Monitoring, Problem Management, Release and Deployment Management, Test and more, are not going away. The integration of ITSM process must be considered throughout the entire value stream and CD pipeline.  None more so than “Change Management”.  Certainly the need for Change Management is increasing not decreasing.

What must go away are over engineered, bureaucratic and outdated process activities.  We must begin to radically rethink the way we incorporate change into the CD pipeline.  Our mission overall is to deliver a “Quality” product or service.

Ok then, what is “Quality”?  Quality not only infers that the service is fit for purpose but also must ensure that it is released into a stable, secure, compliant and available environment.  If not, it does not matter how brilliant the product appears, how much functionality or how easy it is to use.  To accomplish this Change Management must be accelerated.
 
Techniques for Accelerating the ITSM Change Management Process:

Maximize the number of standard changes. This means more pre-approved, pre-authorized changes
Oversee the quality of the DevOps pipeline
Introduce Policy as code “I like this one, think about it! “
Embed and automate communication into the process
Proactive collaboration vs restriction or rejection
Accept user stories/backlog items as RFC’s
And… the most important one is:
Integrate the ITSM Change Management system into the DevOps toolchain
Automate the creation of change records
Automate notifications as changes move through the pipeline
Automate electronic approvals (email, apps, other…)
Build and Automate change models (workflow scripts)

Accelerating Change Management means that we will have to do away with long wait times, hand-offs, laborious documentation and more.  DevOps and Continuous Delivery require ITSM processes to enable Xtreme Velocity.

Learn what it takes to integrate Continuous Delivery into your organization and get certified!

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…