Feeds:
Posts
Comments

Posts Tagged ‘Change’

CMS

At the data level, the CMS may be formed by a combination of physical Configuration Management Databases (CMDBs).

Read Full Post »

CMS

The CMS is a set of one or more connected information sources that provide a logical model of the IT infrastructure.

Read Full Post »

Deployment Plan

For each release, plans should be authorized by Change Management and used to assist in the evaluation of the risk, impact and resource requirements for components of the change.

Read Full Post »

Release Plan

For each release, plans should be authorized by Change Management and used to assist in the evaluation of the risk and impact.

Read Full Post »

In a “perfect world” those could be the representatives for a CAB meeting:
– Change Management team member (could be the manager).
– Configuration team member.
– Application developer.
– Production team member.
– Business member (customer).
– Technical experts.

But the important thing is, rather than having a static list of members, the CAB should include both static and dynamic members who will attend based on the needs for the changes being discussed.

Read Full Post »

The questions that we must ask for a change:
1- Who RAISED the change?
2- What is the REASON for the change?
3- What is the RETURN required from the change?
4- What are the RISKS involved in the change?
5- What RESOURCES are required to deliver the change?
6- Who is responsible for the build, test and implementation of the change?
7- What is the RELATIONSHIP between this change and other changes?

Read Full Post »

Change Proposal

A Change proposal must have a full description of the change together with a business and financial justification for the proposal change.

Must be approved by:
Financial – What’s going to cost?
Business – What are the consequences to the business?
Technology – What are the consequences to the infrastructure? And not doing it?

Read Full Post »

Older Posts »