Do you want to make your Change Management process more efficient?

Change Management has been coming up a lot lately in my discussions with customers.  It could be because I market a product that automates and manages the change process. It seems like IT is finding it harder and harder to manage changes.   Could it be that the IT environment keeps getting more and more complex?

 

Last night I was looking through my ITILv3 class material in search of a definition for an acronym (unrelated to this blog) and I noticed they started the class with a slide on ‘Today’s big challenges for CIO’s. They were all about change and were consistent with what I’ve been hearing from IT people:

-         “Change happens every day and change sends ripples through an organization effecting applications, systems and processes that support it.”

-         “M&A, expansion, datacenter transformation, multi-vendor products all cause the IT environment to be more complex.”

-         “Resources to get the job done are growing scarcer while you are required to deliver higher quality services to customers.”

 

So I went to the Service Transition section and reviewed the Change Management pages.  ITILv3 states:” The objective of the Change Management process is to ensure that changes are recorded and then evaluated, authorized, prioritized, planned, tested, implemented, documented and reviewed in a controlled manner.”

 

This is exciting because the product I market is HP Release Control (RC) which addresses the challenges around the difficulty of managing change and aligns with the objective of change stated above by ITILv3.  

 

Are you wondering what RC is now?  RC is a decision-support tool that ties the change planning and analysis process with operational change execution to help IT Change Managers  and stakeholders make informed approval decisions and gain real-time visibility across all change activity reducing the risk of service downtime.  You can think of Release Control as the connection point between the change process and release execution, linking the two at the point of decision.  By bridging decision-support from the Change Advisory Board (CAB) to the implementation team, customers gain increased visibility and control to make better decisions, from CAB review through post-implementation review.

 

Release control can be integrated with multiple service desks to get scheduled or ad-hoc changes into a single view in what we call a Calendar view.  The Calendar view has an outlook style format.  Through the Calendar a Change Manager can get insight into the risk and impact of change as well as if there are any collisions, blackout periods and maintenance windows, and much more…

 

As I said above, RC aligns with and supports the objective of change management stated in ITILv3, some of which are described in the bullets below:

  • Through a’ Virtual CAB’ RC drives the focus and topics for the CAB meetings in a virtual format.  Alerts generated from RC automatically notifies the impacted parties when a change effects their respective system and fosters the analysis, discussion and the voting of change requests by the necessary stakeholders.  You can assign and tract action items that can be completed before a decision can be made.  You also get an audit trail of all change decisions.
  • Through the Virtual CAB you can facilitate post implementation review and indentify unauthorized changes.  You can document changes that had problems as well as prevent unauthorized changes.
  • The CAB can also get a view of the impact and risk of changes executed in the past.  This process provides you robust analysis and provides a ‘test’ for accurate scheduling of changes.

 

You can tell I am enthusiastic about RC’s capabilities and how it can address the difficultly of change management.  I want to blog more about RC in 2011.  But before I go I want to know if this resonates with you?  Does RC seem like it would make the change process in your environment more streamlined and efficient?

 

Comments
rahul_sinha08 | ‎12-18-2010 11:08 AM

Hi Ann,

 

I wanted to ask this: Does the Release Control (RC) from HP is a Change Management tool or is it a Release Management Tool?? If it is a change management tool, then what would happen to the CM module which is part of the HPSM? If it is a Release Management tool, why does it not talk about releases then changes? 

 

I am currently trying to implement RC for one of our clients as a Release Mgmt tool (they already have HPSM for CM). My concern is RC doesn't follow the ITIL V3 process for Release Mgmt. Please correct if I am wrong. The major functionality which is missing is bundling of changes in a release package. 

 

Regards

Rahul

Hamptow | ‎01-18-2011 02:07 PM

Hi Ann,

Thanks for the idea for RC.  I have been an HPQC Administrator for years and also rolled out Service Management (Altiris) that I interfaced reporting to HPQC for Test & Defect Management, but in my new Role I am implementing HP Service Manager for IT and HPQC and would like to know if you have any suggestions for reading on these and how they would interface with RC?

 

Thanks for your time.

 

Regards,

Bill

Leave a Comment

We encourage you to share your comments on this post. Comments are moderated and will be reviewed
and posted as promptly as possible during regular business hours

To ensure your comment is published, be sure to follow the Community Guidelines.

Be sure to enter a unique name. You can't reuse a name that's already in use.
Be sure to enter a unique email address. You can't reuse an email address that's already in use.
Type the characters you see in the picture above.Type the words you hear.
Search
Showing results for 
Search instead for 
Do you mean 
About the Author
Ann Keffer is a Product Marketing Manager for the HP Business Technology Optimization Business (BTO). She is responsible for out-bound mark...
Featured


Follow Us
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.