Home > Articles > Information Technology

Defining ITIL Change and Release Management Processes

  • Print
  • + Share This
This chapter starts with a generic description of how to define any process at four levels. After you understand the basics, the ITIL suggested high-level processes are introduced, followed by specific suggestions about how to customize your own change and release management processes.
This chapter is from the book

The heart of ITIL is in processes and the disciplines surrounding them. Thus, it should be no surprise that early in the planning for change and release management, you need to begin defining processes. Although version 3 of the IT Infrastructure Library defines the processes in more detail than any previous version, it still doesn't describe exactly which process every organization should use. This is because one of the best practices is that each organization should define its process somewhat differently.

This chapter starts with a generic description of how to define any process at four levels. After you understand the basics, the ITIL suggested high-level processes are introduced, followed by specific suggestions about how to customize your own change and release management processes.

How to Define a Process

Like most specialties, process engineering uses its own vocabulary. The words aren't complex or difficult, but they are used in a specific context and must be understood that way. To work effectively with process engineers, you must know this vocabulary. This section introduces the important terms and concepts used to define a process. Figure 3.1 shows the steps required to build out a process.

Figure 3.1

Figure 3.1 Five basic steps are needed to create a process.

Start with Process Flow

At the onset of defining your process, you need to grapple with what is meant by a process. Although more technical definitions are available, the working definition of a process is a sequence of defined actions that produces a measurable and desirable outcome. Because a process is a sequence, the place to start with definition normally is a flow diagram of some sort. Whether you favor a "line of visibility" diagram that delineates the different roles in the process or a simple flowchart that captures only the steps, your organization should adopt a standard way of defining a process flow. Look around for other process documents, and copy whatever style is in use for your organization.

Creating a workable process flow requires a solid starting point. Fortunately, the ITIL service transition book provides a solid start. In Chapter 4 of that book, you'll find some excellent sample process flows that can serve as a starting point. If your organization already has change management and/or release management processes documented, those can also serve as good reference points.

After establishing a starting point flow, the next step is to look back at the requirements you documented. Look very closely at the process requirements, and see if any of them dictate that you change your starting flow in specific ways. It would be unlikely at this high level, but occasionally a requirement will cause you to add a step to an overall flow.

Be sure not to get too detailed in your high-level flow. A good rule of thumb is that the top level should fit on a single page. Most of the process requirements will be around the details rather than the high-level process. Those details will be worked out eventually, but you have the greatest chance of success if you start with a single sheet that all your stakeholders can agree is the top level of the process.

After you have used existing starting points and your own judgment to define a high-level process flow, it is time to validate it. Take the single sheet to your sponsor, your stakeholders, and the project team. Get their ideas and incorporate them. Be sure to keep everyone aligned with the scope of your project. This is not a second round of requirements gathering, but an attempt to meet the requirements and scope you have already defined. It is important, however, that the high-level flow meets everyone's understanding of the project scope, because you are about to base many hours of work on this single page.

Frequently one or more activities on the high-level flow will be worthy of a separate flow by themselves. In the language of the process engineer, these are subprocesses. Identify these subprocesses as you validate the high-level flow, and work with the stakeholders and project team members to build these flows as well. As before, constrain each to a single sheet of paper, and focus on getting the flow documented in a consistent format. The subprocesses do not need to be especially detailed at this point, but they should provide enough information to allow later definition of the details.

As soon as all the flows are complete, you have the basic outline for all the process work. From these simple flows, you will determine which policies need to be defined, how many procedures will be written, and ultimately how many work instructions need to be documented.

Identify Needed Policies

The next term to understand is policy. A policy is an axiom or rule that is always true because your organization says it is true. Change and release management abound with policies, and throughout this chapter, you'll find many examples of policies that you may want to adopt for your process work. For example, many organizations insist on a policy that no IT component or service can change without an authorized change record. Policies are declarative statements about how things should work, and many times these policies result directly from the requirements.

When the high-level process flow and subprocess flows are done, the next step is to read the requirements and determine where policies will be needed. One clue is that policies often are associated with making a decision. Look at the decisions on your process flows, and determine how that decision will be made. Is there a policy statement to be defined? Unless the decision is very simple, you will probably want to provide some guidance in how it is to be made, and that's the perfect reason to create a policy.

Not all policies are large and encompassing. Instead of a single grand policy on change approvals, let the process flow guide you in creating smaller policies on change advisory board (CAB) membership, voting rules, handling of emergencies, and so forth. Try to keep the policies focused on one area at a time, and later you can combine them into a single policy document if that's more convenient to manage.

Create enough policies that no important decision or action is left to the imagination of one person. That is when you know enough policies have been defined.

Create Procedures

Procedures are the meat of the process definition. They are the narrative description of the step-by-step actions that someone will take to follow the process. Although the high-level flow provides a good overview, the procedures are the details of how to actually execute the process.

Procedures should be detailed enough that two people executing the same process step will always get the same result. They do not need to be so detailed that two people following them will use exactly the same method to get the desired result. Finding the correct level of detail requires an understanding of your organization and the skill level of the people who will be assuming the change and release management roles.

Procedures normally are documented as a numbered list of the specific steps that need to be taken. Not every activity in the process and subprocess flows will require a procedure to be written, but many of those steps will. If the outcome of an activity on the high-level flow is critical, or if that activity will involve a lengthy set of steps, document that activity with a procedure.

Often procedures are written into the same document as the high-level flows. This is a good format, because it keeps all process documentation in one place and is easier to maintain. On the other hand, if you have many procedures and policies, keeping everything in a single document can result in a very long document that is difficult to review and read. Some organizations choose to keep their process and procedure documentation online in a web page or wiki. That format lends itself much more readily to having each procedure and policy written as a separate short document that can be indexed from a process home page.

Document Work Instructions Where Needed

Sometimes procedures can get too lengthy and cumbersome, or the same set of steps needs to be repeated in multiple procedures. This is where a work instruction can be useful. A work instruction is a very specific bit of guidance on how to achieve a specific task within the process domain. For example, in your change management process, you may have several procedures that start with someone looking for a specific change record in an online tool. If the tool has been in your organization for a while and everyone knows how to look up records, you can probably just include a single step in every procedure that says "Look up the change record." On the other hand, if the tool is new, you might want to document exactly how to look up a record. You could do that in one place in a work instruction and refer to it in your procedures.

Normally, work instructions are tool-specific and procedures are not. This is a good practice, because it allows you to change tools in the future without having to rewrite your procedure documents by simply creating additional work instructions. If this is important to your organization, you will have general procedures with many more work instructions.

Keep the work instructions at a higher level than a tool user guide, however. They should be used only to describe specific uses of a tool where many options might be available. For example, your release management tool might support a variety of approaches to documenting a release policy. You could write a work instruction that directs people to always follow a very specific method. This ensures that people within your release management team always use the tool in the same way regardless of the latitude offered by the software publisher.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020