Skip to main content

Why RCV?

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 Release Control and Validation (RCV) provides in-depth knowledge of the ITIL 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 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 more information on Release, Control, and Validation:  click here

Comments

Popular posts from this blog

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem

What Is A Service Offering?

The ITIL4 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 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.               Note: Goods may not always be provided for every Service Offe

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