Skip to main content

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 deliver value, but that we design and deliver services, BETTER, MORE, FASTER THAN EVER BEFORE and at the same time we are being COST effective.

The role of Release Manager, although it is central to the release and deployment process, is much broader in scope than many organizations or managers realize. This role in Best Practice is separate from Change Manager and from the actual Validation and Testing Manager or even the Change Evaluation role. Frequently these roles will be assigned to one or more persons. It does not mean that you have to open several new req's or that you will have to replace people. What this does mean is that a clear and concise understanding of these processes, roles and functions must be clearly understood in order for organizations to really reap the benefits that they expect from change and release efforts. Not only do we need to understand the dependencies, but also the workflow of how we can quickly interface with the various functional teams to respond quickly. Without the proper knowledge and skill for these best practices, an organization could overtime improve but will be less likely to reap the type of optimization and benefits that they had hoped for. Everyone will agree that we can always do better with what we have.

The course ITIL V3 Release Control and Validation (RCV) provides in-depth knowledge of the ITIL V3 RCV areas: Change Management, Release and Deployment Management, Service Validation and Testing, Service Asset and Configuration Management, Request Fulfillment, Change Evaluation and Knowledge Management; most importantly the roles and the process interfaces and dependencies. Best practice can help get the bigger picture, identify gaps, and allow for the practitioner to be enabled for success. Business requirements are dynamic and we (throughout the design & delivery) must also have processes and models in place to meet those constantly changing business requirements.

In summary, the ITIL V3 RCV processes, integration and knowledge enable:
  • response to CHANGING Business Requirements
  • consistent and Repeatable Workflow that result in and successfully deploy faster into the environment
  • your staff and your organization for real success resulting in less rework and greater productivity
  • results in cost savings for the business
  • the ability to deploy changes quickly with less defects and therefore less business and customer disruption
  • risk reduction while complying with governance and audit requirements
  • overall improvement in quality resulting in increased value for consumers
For a more detailed understanding, ITIL 4 Specialist modules "Create, Deliver and Support" offer comprehensive coverage of these practices in a modern context.

Comments

Popular posts from this blog

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.”  Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...

What Is A Service Offering?

The ITIL 4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group.   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions 1. Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.      ...

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

This article was originally published in 2015. With the Introduction of ITIL 4, some of this best practice has changed. See  ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...