November 22, 2006
Release Management Management Tools and Techniques
All processes need quality control checks. They also need someone to manage and assure a successful process. In ITIL release management, the controller of the release management process is the release manager.
The release managers duties are:
- To act as an Advocate - One of the release manager's roles is to clearly communicate the benefits of adopting release management practices to system users, company managers, and to colleagues in the IT department. Think of it as a one man marketing campaign.
- To be an Investigator - Another important role of the release manager is investigating how and why new configuration items make their way into the live environment without following the release management process. This would be commonly referred to as auditing and investigating.
- To be a Trainer and communicator - The release manager is the point of communication between the release management process and other IT service processes. This role also includes providing written and oral instructions for introducing new releases to the customer base. It is really a good thing to centralize this because with centralization comes standardization.
When I first started in IT, we had this product upgrade that was overwhelming and time consuming. Every two months, we had to make the product unavailable for half a day toupgrade the system. Talk about disturbing the operations of the business. Thankfully we improved upon the implementation pattern and eventually eliminated that application. A successful release management process is determined by controlling the introduction of new releases without creating disruptions within the company. Here are four key performance indicators used to determine the success or failure of your release management process:
- Schedules and budgets – Completing releases on time and within budget is a good indication that the process is successful.
- Failures and backouts – Having a low occurrence of failures and back outs is an indication that releases have been properly planned and executed. Backing out a release normally equates to the fact that the release wasn’t tested thoroughly on the company infrastructure or with other systems.
- DSL and DHS - A complete and up-to-date definitive software library (DSL) and definitive hardware store (DHS) indicate release management is exercising adequate control over new releases. The control of CIs in new releases ensures that they conform to planned standards.
- Records and updates - The ability to plan and execute releases depends on an accurate configuration management database (CMDB). Release management must provide information about the changes new releases make to the infrastructure so the database will remain accurate. Release management's actions affect the efficiency of the rest of the company.
As the old saying goes it is difficult to manage that what you cannot measure. There are several managerial reports that assist in determining the opportunities for process improvement and rate how well the release management program is maintaining.
- by level - A report that shows the number of successful releases illustrates the degree of control the release management process exercises over the introduction of new hardware and software.
- actual versus plan - A report of successful releases should show the number of major, minor, and emergency releases. A report of successful releases should compare the actual time and cost of implementing releases to the planned time and cost.
- number of releases that failed - A report of the number of releases that failed reveals opportunities to improve the release management process.
- number of problems or errors caused by releases - A report of known problems resulting from releases provides an indication of inadequate planning or testing of releases. Although it's sometimes difficult to own up to mistakes in planning, this type of report provides a basis for discussing plans for improving the release management process.
The members of the release management team who plan and execute releases must pay close attention to details. The duty of the release manager and other senior company managers is to look at the big picture and direct the action with correction or preventative steps.
Posted by Elyse at November 22, 2006 5:23 AM
Comments
Post a comment
Did you miss?
IT Governance, the decisions needs by whom
Finally passed the test
Managing in light of McGregor's Theory X and Theory Y
CMMI
Kicking HIT Leadership Up a Notch
That's just some mumbo jumbo project management BS
Outcomes - The tactic to get to the strategy
Nurse Call, VOIP, and Wi-Fi: Its just cool when things come together!
Finally passed the test
Managing in light of McGregor's Theory X and Theory Y
CMMI
Kicking HIT Leadership Up a Notch
That's just some mumbo jumbo project management BS
Outcomes - The tactic to get to the strategy
Nurse Call, VOIP, and Wi-Fi: Its just cool when things come together!
Archives
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
August 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
November 2005
October 2005
September 2005
August 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
August 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
November 2005
October 2005
September 2005
August 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
Blogs
Cafe au Lait
Joel on Software
David Ross
Edward Prevost
Martin Fowler
The Health Care Blog
The Tales of Hoffman
The Business Word
Medical Rants
Christina's Considerations
Paul Levy
HIS Talk
Appropriate IT
Candid CIO
Joel on Software
David Ross
Edward Prevost
Martin Fowler
The Health Care Blog
The Tales of Hoffman
The Business Word
Medical Rants
Christina's Considerations
Paul Levy
HIS Talk
Appropriate IT
Candid CIO
Subscribe
© Copyright 2003 - 2007 Elyse Nielsen
RSS feed




