Posted: Mon Mar 24, 2014 9:23 pm Post subject: Change Categories
I realise this is a difficult question to answer and differs from business to business, however I’m giving it an airing for feedback anyway.
We are looking to drive change approvals based on the V3 change types and categories.
So for a Normal Change i am looking at;
Major 20d lead time- Multiple business departments affected, introduction of a new service, decommissioning current live service.
Significant 10d lead time - Downtime required, Service degradation required, No back out available only forward fix.
Minor 5 d lead time - Build of a new single server (non-standard), Configuration Change no negative impact.
Both Major and Significant changes will require a pre review via CAB Agenda and possible a detailed walkthrough from the requestor / sponsor.
The Minor Change will be represented on the CAB day and potentially approved in the meeting.
The other thing to understand is that we are restricted to Tin and String changes and will occur at some point. The approval to proceed with a build from project (financial, strategy and resourcing) is controlled via a different project process. The Project manager interacts with change when actual environmental changes are required.
Basically, does this seem sensible? have we missed the point and can you think of criteria i can put into Minor.
Im not sure I get the first point about the realities of the corporate environment? My idea of the time frames is to offer some protection to the business and to put an end once and for all to engineers and project managers requesting changes at the last minute and expecting approval before CAB.
This will also give us some time to undertake assurances, peer reviews, security sign offs etc.... whilst still allowing an avenue for true fast track changes. Not where someone forgot and now needs a favour.
Configuration management is primitive within the organisation, but does exist for application deployments, however Change and Release Management are combined into the same team.
RFC forms we use have the scope for the full implementation instructions.
All the areas you have mentioned are in scope
Applications: - Rollout - patching -
Network - Although more difficult for me to
I suppose what I am asking what else could be put into the minor category. I feel saying all changes that have "no impact" and "low Risk" to production services is a big catch all that could bite us when we try to apply categorisation.
Joined: Sep 16, 2006 Posts: 3366 Location: London, UK
Posted: Fri Mar 28, 2014 11:57 pm Post subject:
To my first point. The defintion of how you differentiate the types of changes should be based on the IT environment at hand
So for example: The CM scope is only networks so there is a fast turn around and very little testing as the majority of the work is either enable or disable F/W ports / IP.
So there would only need to be - Emergency (Fault fix), Normal Change
These are speedily approved (almost presumed)
However, there are a few changes that involves other work than F/W disable enable port /IP so you have Major
So you have 3 Change Classifications - Emergency and Major and Normal
Emergency for Fault fixes only
Major and Normal for everything else. The CAB only discusses the Major but the CM merely tracks the normal for statistical purposes _________________ John Hardesty
ITSM Manager's Certificate (Red Badge)
Change Management is POWER & CONTROL. /....evil laughter
I think it's entirely specific to your business needs but we use fairly standard catagories.
This is ripped out of our change management policy which I wrote.
A standard change is a change to a service or infrastructure for which the approach is preauthorized by change management. A standard change has an accepted and established procedure to provide a specific change requirement. The crucial elements of a standard change are that:
• The change is in the Standard Change list documented by Change Management
• The tasks are well known, documented, and proven
• Authority is effectively given in advance and authorisation is not required from CAB or Change Manager
• The impact is low and always well understood
• The risk is low and always well understood
A minor change is any change which is not a standard change, a major change or an emergency change. All minor changes must be submitted to the Change Manager for approval once the change has secured resource and availability from the Change Implementer to be completed. Once approved, the Change Implementer can carry out the change.
A major change is any change which is considered to be of high risk, high impact or may be significantly visible both internally and externally (such as the deployment of a new customer service capability). Release as defined in the companies Release Management policy are also considered Major changes. All Major Changes must be submitted to the CAB for review, should further discussions be required an emergency CAB meeting may be convened.
Emergency changes are usually initiated in response to a critical IT situation, often an incident or problem requiring immediate action to restore service or prevent service disruption.
The emergency change category is reserved for changes intended to repair an error in a service that is negatively impacting the business to a high degree.
Effectively, the emergency change procedure will follow the normal change procedure except that:
• Approval by Change or Incident Manager if neither can be contacted and sufficient business justification exists the change may be carried out with retrospective authorisation sought.
• Testing may be reduced, or in extreme cases forgone completely, if considered a necessary risk to deliver the change immediately.
• Documentation, such as updating the change record and configuration data, may be deferred, typically until normal working hours.
The number of emergency changes proposed should be kept to an absolute minimum, because they are generally more disruptive and prone to failure with corresponding negative impacts to service availability.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum