open
  1 (866) 866-2320 Resources Events Blog

Planned vs. Actual Change: Why is IT still Flying Blind when it comes to Changes?

Blog

Planned vs. Actual Change: Why is IT still Flying Blind when it comes to Changes?

About

This content is brought to you by Evolven. Evolven Change Analytics is a unique AIOps solution that tracks and analyzes all actual changes carried out in the enterprise cloud environment. Evolven helps leading enterprises cut the number of incidents, slash troubleshoot time, and eliminate unauthorized changes. Learn more

 

Here’s a true story:
An application is moved to production.

Users start seeing weird data and strange transaction results.

So, they start to complain.

Your IT Team works frantically for HOURS to figure out the root cause of this performance issue.

The cause?

Apparently, the application’s connection string still points to the staging database…

This minor misconfiguration parameter turned into a high impact incident.

This is not unusual.
In fact, according to Gartner, 85% of incidents can be traced back to changes like this.

image

IT is “Flying Blind”

So why does this happen?

Why does IT struggle to prevent the majority of the performance, compliance and security incidents caused by changes?

We believe it is mainly because when it comes to changes, IT is “flying blind”.

Yes, change requests are managed in the service desk, and CI/CD pipeline is used for logging every delivery and deployment activity. But all of these tools do not know what ACTUALLY changed.

There is an important distinction that needs to be made here between:
Planned Changes vs. Actual Changes

Actual changes are not...

  • Planned change requests in a service desk
  • Not the deployment artifacts packaged for deployment through CI/CD pipeline
  • Not deployment scripts executing deployments
  • Not metrics and log events collected by performance management tools

All of this information will give an idea about the changes IT has INTENDED to implement... but not what was actually implemented.

So when I say ACTUAL changes, I mean specific granular updates executed anywhere in the environment, from application to infrastructure, as the result of the planned and unplanned deployment activities, delivered automatically or manually.

Without visibility into ACTUAL changes, IT cannot easily identify the changes that cause the issues.

Neither can IT succeed in effectively evaluating the risk of the detailed changes before they cause any issues.

...Enters Evolven.

Evolven tracks all actual changes at a granular level and automatically detects any discrepancies between the approved changes.

Evolven allows IT Ops, DevOps, CloudOps, and other teams managing the stability of their business systems and the underlying infrastructure, to quickly view and fix any unauthorized, inconsistent or incomplete changes to effectively prevent and troubleshoot performance, stability and compliance incidents.

Learn more and set up a time to see Evolven in action here.

About the Author
Nicole Prybula

Field Marketing Manager