Skip to main content

Posts

Showing posts with the label Change Management

Confessions of a Change Manager

By Donna Knapp   At one point in my career, I was a change manager. I ran my company’s change advisory board (CAB), and I spent endless hours trying to convince project managers to submit requests for change (RFCs). Despite my best efforts, I invariably had to explain, fairly often, that ‘poor planning on your part does not constitute an emergency change on mine.’ At that time, the change manager role was one of the many hats that I wore. My ‘real’ job was service desk manager. We called it a ‘hotline’ then and so yes… it was many, many years ago. In that role, I and my team saw the impact of poorly executed and failed changes. We dealt every Monday morning with the chaos that came out of the massive changes made over the weekend. That was then. Since then, much has changed. But it was through that lens that, more than 10 years ago, I first started researching a movement in the IT industry called DevOps. At the time, it was early days for DevOps and individuals and organizations were s

ITIL 4 Change Enablement: Streamlining Your IT Service Management

Change Enablement is a practice within the ITIL 4 framework that focuses on managing changes to IT services, systems, and infrastructure in a controlled and efficient manner. The primary goal is to minimize the negative impact of changes while maximizing their benefits. This involves assessing, authorizing, and overseeing changes to ensure they are implemented smoothly and successfully. The Importance of Change Enablement Change Enablement is a critical practice for managing the complexities of IT service management. By adopting a structured approach to change, organizations can minimize risks, ensure business continuity, and remain agile in the face of new challenges.  1. Risk Mitigation : Uncontrolled changes can lead to service disruptions, security breaches, and compliance issues. Change Enablement ensures that all changes are carefully evaluated and authorized, reducing the likelihood of negative outcomes. 2. Business Continuity : By managing changes effectively, organizations can

The Top Benefits of ITIL

Stronger alignment between IT and the business: Historically IT has not been a participant in helping to create business strategies, it was normally in the role of supporting them. Recently, with the speed of innovation impacting businesses position in the marketplace, IT has been playing a greater role in helping to develop that business strategy. The ITIL framework enables IT to act as a service provider and become a core and more strategic part of the business. Pre-defined processes and best practices from the ITIL framework enable businesses to react quickly to today's rapidly changing technology landscape, focus on innovation and ultimately keep customers satisfied. Improved service delivery and customer satisfaction: Event, incident and problem management processes included within the ITIL framework enable businesses to review performance, perform root cause analysis, resolve issues and through problem management, prevent future incidents from occurring and allows us

Digital Transformation - What Is It?

Customers are empowered and connected. To stay relevant many organizations are asking “how can we evolve with the digital era?” To lead the change, we must understand it.  It is likely that in the next one to five years your organization will focus on digital transformation in three or more of these areas: Artificial Intelligence / Machine Learning Defined as the study of " intelligent agents " on any device that perceives or learns its environment and takes actions toward success at a specified goal. The Internet of Things (IoT) The IoT refers to the connection of devices (other than typical computers and smartphones) to the Internet. Today things like cars, kitchen appliances, and even heart monitors can all be connected through the IoT. Who would have known that we might need to add items such as drones to an asset registery and learn how to manage them? And as the IoT grows in the next few years, more devices are and will continue to join that list. (Editor'

Agile Change Management

I always hear people say ‘Don’t like the weather, wait an hour it will change’.  The one constant in our lives is change. In business today, customers, users and stakeholders all have the expectation that as IT service providers we can and should be able to handle change requests at an ever-increasing pace.  Yet they still have the expectation that an appropriate response to all requests for change entails a considered approach to assessment of risk and business continuity, change impact, resource requirements, change authorization and especially to the realizable business benefit. For us to be able to do change management in an Agile environment, does that mean we must give up those requirements for speed and agility? The purpose of Change Management is to control the life cycle of all changes enabling beneficial changes to be made.  I was once told by a very wise thought leader ‘Being agile is a state of mind.  It’s more perspective than prescription.’  Why can’t we have a

Process Practitioner Examples – Roles and Responsibilities Revisited

Assigning clearly defined roles and responsibilities are critical to the success of every process. These roles need to be defined early and reviewed periodically to ensure proper training, communication and education.  A process without clearly defined roles will fail at some level.   There is a very clear distinction in the activities or the roles that are played out by individuals in your organization.  You should determine and communicate who is accountable and who is responsible for the process activities.  A role is like a hat.  One individual could wear two or more hats.  Watch out for titles.  You might have a title such as Service Transition Manager.  What role(s) would this individual fulfill? It all depends on WHO is best suited for the role or task that needs to be performed when it comes to assigning roles. The Service Transition Manager could be accountable or OWN the “Release and Deployment” process but might also be a practitioner and be responsible to perform task

Site Reliability Engineering

Site Reliability Engineering (SRE) is a discipline that incorporates aspects of software engineering and applies that to operations with the goal of creating ultra-scalable and highly reliable software systems.  Google’s mastermind behind SRE, Ben Treynor, describes site reliability as “what happens when a software engineer is tasked with what used to be called operations.” Historically, Dev teams want to release new features in a continuous manner (Change). Ops teams want to make sure that those features don’t break their stuff (Reliability). Of course the business wants both, so these groups have been incentivized very differently leading to what Lee Thompson ( (formerly of E*TRADE) coined the “wall of confusion”.  This inherent conflict creates a downward spiral that creates slower feature time to market, longer deployment cycles, increasing numbers of outages, and an ever increasing amount of technical debt. The discipline of SRE can begin to reduce this dilemma by

Why RCV?

Note: this was originally published in 2016 and explains the ITIL V3 lifecycle phase "Release, Control, and Validation (RCV)." In 2024, the ITIL 4, the concepts of RCV are integrated into various practices, notably Change Enablement, Release Management, and Service Validation and Testing, which are essential for managing and ensuring successful service changes, releases, and validations.  For a more detailed understanding, ITIL 4 Specialist modules like " Create, Deliver and Support " offer comprehensive coverage of these practices in a modern context. --- I was recently asked the following: “I want to take the “Release, Control and Validation” (RCV) class. As a Release Manager, I know it will help but I need to justify this for my manager. What is the value of taking this class?” Every organization can be effective with release and deployments. What is needed today is for us not only to get the job done but to do it efficiently. Efficiency infers that we deliv

What is RCV?

Note: this was originally published in 2016 and explains the ITIL V3 lifecycle phase "Release, Control, and Validation (RCV)." In 2024, the ITIL 4, the concepts of RCV are integrated into various practices, notably Change Enablement, Release Management, and Service Validation and Testing, which are essential for managing and ensuring successful service changes, releases, and validations. For a more detailed understanding, ITIL 4 Specialist modules like " Create, Deliver and Support " offer comprehensive coverage of these practices in a modern context. --- RCV stands for Release, Control and Validate. These are critical activities that are required for every deployment. Proper Release, Control and Validation (RCV) is achieved as a result of integrated process activities. In today's dynamic business climate, service outages cause real bottom line impact to the business. Mature processes are critical in enabling IT organizations to smoothly transition new and ch

Change Evaluation

I often get asked where change evaluation takes place.  Isn’t it part of change management?  It is a separate process however it is driven by change management and is triggered by the receipt of a request for evaluation from Change Management. Inputs come from several processes including the SDP and SAC from Design Coordination, change proposal from SPM, RFCs, change records and detailed change documentation from Change Management.  It holds discussions with stakeholders through SLM and BRM, testing results from service validation and testing to ensure that its members have a full understanding of the impact of any issues identified and that the proper risk assessments can be carried out against the overall changes and in particular the predicted performance, intended effects, unintended effects and actual performance once the service change has been implemented. The purpose of change evaluation is to provide a uniform and structured means of determining the performance of a

Continuous Delivery

Continuous Delivery is a software development practice where software is always in a releasable state.   Teams produce software in short cycles, ensuring that the software can be reliably released at any time.  By relying on automated testing and deployment, as well as ensuring collaboration and communication between development and operational teams (DevOps), the goal of building, testing, and releasing software faster and more frequently can be achieved. This approach can help to reduce the cost, time and risk of delivering changes by allowing for more incremental updates to applications and configuration items (CIs) into production.  A straightforward and repeatable deployment process is important for continuous delivery and will be critical for operational processes such as Change Management and Release and Deployment Management to be agile and robust in the DevOps environments where continuous delivery will be part of best practices.   Continuous Delivery is sometimes co

The Customer Experience

We are all customers of someone right?  What was your last customer experience like?  Was it so good that it completely changed how you thought about the product or the organization you were receiving services from? On the other hand was the service you received so poor that you vowed never to use their products or services ever again.  We have all been in those situations. You may not have realized it, but how that interaction was designed can have a huge impact on the perception you, the customer, walk away with.  I recently read a series of articles in the September issue of Harvard Business Review magazine.  The entire series was titled “The Evolution of Design Thinking” - It’s no longer just for products. It speaks to how executives are using this approach to devise strategy and manage change.  I can’t tell you what an absolute must read this is for all.  It will make you take a second look at how you design, deliver and support the services to your customers. For me personally t

Change Proposals

When an organization is planning on a major change that will incur significant cost, risk, time and engagement of resources along with organizational impact, it is best practice to initiate this activity through the Service Portfolio process.  Before this new or significantly changed service is chartered, it is important that it be reviewed for how it may impact the short, medium and long term support of other services currently being delivered, the pool of limited resources that will be utilized for this undertaking and on the change schedule itself. The Change Proposal is used to communicate a high level description of the change and is normally submitted to Change Management for authorization.  Authorization, however, is not an approval for implementation, but is a measure to allow the service to be chartered so design activity on the service can begin. In some cases the proposal may be created by someone other than Portfolio Management, such as the PMO or SMO. This high le

Assessing and Evaluating the Change

All changes need to be assessed and evaluated.  Changes that are considered significant should be subject to a normal change evaluation in which we have well defined criteria for making this determination.  In this blog we will focus on the assessment side of the equation. A logical place to begin assessing the impact of changes on services and configuration assets would be the use of the "Seven Rs of Change Management".  Without these questions being answered a proper impact assessment could not be completed.  When leading an impact and resource assessment several items should be considered.  At the top of the chart we need to determine if there will be an impact to the customer's business operations.  Next we might want to know what the effect will be on infrastructure, individual customer services and their performance, reliability, security, continuity and ability to handle various levels of demand.  Additionally we will need to understand what the current change sc

Release, Control and Validation (RCV) – Service Management Secret Ingredients

In today's dynamic business climate, service outages cause real bottom line impact to the business. There are documented best practice processes and known critical success factors and yet outages that throw support organizations into reactive firefighting turmoil are far too common. Mature processes with just enough control are needed to smoothly transition new and changed services into production, helping to ensure stability for IT and the business.  Most organizations will confirm that they do have Change and Release Management processes in place.  Service Providers will usually have some level of Service Asset and Configuration Management control.  There is generally a lot of buzz and focus on three core processes for Service Transition and the success and integration of these three are critical to business success.  Three Core Processes for Service Transition are: Change Management Service Asset and Configuration Management Release Management Most IT organizations

Visible Ops & Agile Service Management

I highly recommend The Visible Ops Handbook by Gene Kim, Kevin Behr and George Spafford. There are a lot of intersections between Visible Ops (VisOps) and being Agile.  In fact, following Visible Ops practices allows you to achieve an Agile perspective in a shorter time scale.  There is an area in particular where I think alignment between VisOps and Agile is very strong. One of the four tenets of the Agile Manifesto is that we value “Responding to change”.  This is further underpinned by the principle “Welcome changing requirements, even late in development”.   Agile processes harness change for the customer’s competitive advantage.   This also ties us to the goal and objective of Agile Service Management in “Improving IT’s entire ability to meet customer requirements faster”. Responding to change does not equate to bypassing process or controls.  Every business decision triggers an IT event.  Industry statistics tell us that 80% of outages are a direct results from poor

Visible Ops

Anyone who has worked in Information Technology knows that today, there is and always will be improvement opportunities available to our organizations.  This is especially in light of the pace of change that is taking place in all market spaces and the level of customer expectations that accompanies that change. If you have worked in IT for a number of years, you may remember when change was not welcomed. Well the good old days weren’t always that good and tomorrow ain’t as bad as it seems (Billy Joel).  The challenge is in getting started. If……. ·        the processes that are currently being engaged are not as efficient and effective as you would like ·        you are finding that your environment isn’t as stable and reliable as it should be ·        that when you make changes to your environment it generally results in an outage and prolonged and repeatable firefighting then ……. I recommend that you read The Visible Ops Handbook by Gene Kim, Kevin Behr and Geor

The Difference Between Change and Release Management

A reader recently asked me to comment on the difference between Change and Release Management. The first question “Is it a request or proposal?” is a good one.  When we use the term proposal, normally we are speaking about major changes that will involve significant risk, cost, or organizational impact.  Proposals are normally initiated by the portfolio management process.  They can also be submitted by a program or project management office.  Again remember that each organization is unique and how they do this and at what level it takes place can be different from organization to organization. This is defined at a high level, but the details necessary will depend on the organizational requirements.  For the most part, before the new or significantly changed service is chartered it is critical that the proposed change be reviewed for its potential impact on other services, shared resources, and the change schedule. These proposals are submitted to change management before being ch