Understanding the ITIL Trinity of Configuration, Change and Release Management June 28, 2007 2:00pm EDT, 11:00am PDT George Spafford, Principal Consultant Pepperweed Consulting, LLC “ Optimizing The Business Value of IT” www.pepperweed.com
Change Management Is the set of standardized processes and tools used to handle change requests in order to support the business while managing risks. [Risk Management]
Release Management Uses formal controls and processes to ensure requirements are met and safeguard the production environment. [Quality Management]
Configuration Management Focuses on tracking and documenting configurations and then providing this information to other areas including Change and Release Management. [A combination of Knowledge Management and Information Broker]
The three process areas must work together and share information.
ITIL tells us that “Configuration Management provides a logical model of the infrastructure or a service by identifying, controlling, maintaining and verifying the versions of Configuration Items (CIs) in existence.”
Configuration Management provides information about CIs and their relationships to all the other processes
So Change Management can assess impacts
So Incident Management knows where to look next or who to notify
The Configuration Management Database (CMDB) is the nerve center of IT
It relates all the data together, provides workflows, access to files, etc.
It can be one database or integrations into multiple sources (federated models)
The CMDB contains the data and processes that binds the ITSM processes, services and the organization together
These are categories of data that you must track and are modeled using data tables
Hardware – PCs, Servers, Network Equipment, etc.
Software – Operating Systems, Applications, Tools, etc.
People – IT staff, business staff, vendors, etc.
Accommodations/Environment/Facilities – Locations, data centers, wiring closets, etc.
Data – tables, interfaces, etc.
Documentation – Policies, work instructions, SLAs, rollback plans, incident records, problem records, request for change, etc.
Business Processes – sales, accounts receivable, etc.
IT Services – What IT provisions to enable the business
An ITIL “secret” is that nearly everything is a CI. The establishment of these CI-types, their attributes and relationships enable a logical model of IT
Note – Never do Configuration Management First Either do Change and Configuration together or Change and then Configuration Management. Change Management must be present to control the updating of the CMDB
British Educational Communications and Technology Agency (BECTA) http://www.becta.org.uk/tsas
IT Process Institute’s Visible Ops Methodology http://www.itpi.org
PMI Project Management Body of Knowledge http://www.pmi.org
Projects in Controlled Environments version 2 (PRINCE2) http://www.prince2.org.uk/web/site/home/Home.asp
For additional material, use Google and search on keywords such as
“ SDLC template”
“ Project Management template”
“ Release Management template”
“ Release Plan”
“ Rollout Plan”
“ Fallback Plan”
Thank you for the privilege of facilitating this webcast George Spafford Principal Consultant Pepperweed Consulting Optimizing the Value of IT [email_address] http://www.pepperweed.com Daily News Archive and Subscription Instructions http://www.spaffordconsulting.com/dailynews.html