|
Change Management Strategy
Need to review change management strategy for an
information management strategic plan and want some
practical timesaving suggestions?
Change management provides
a disciplined process for
introducing changes into the production environment with minimal
disruption to ongoing operations.
This is a critical component of
successful information management
and it is important to gain a good understanding of the "as is"
situation to determine what changes might be required.
A change management methodology should
include the following
objectives:
- To formally
initiate a change through
the submission of a change request (CR);
- To determine
impact on existing documentation and configuration items
e.g.
requirements, architecture documents and/or software configuration
items;
- To establish a formal process for
authorizing
change;
- To plan
the
deployment of any change which may
impact the production environment;
- To manage the deployment of releases in a
consistent manner with the least
impact
upon production; and
- To
conduct a post-implementation
review to determine if the change has
achieved objectives and whether to keep the change or back it out.
Change management strategy checklist
Be sure to consider the following change management items during the
information management strategy analysis:
 Does the methodology provide
an authorization
and tracking
processes to ensure only approved changes are deployed?
Does it require
a configuration
management process to
assess the impact of change on all potential configuration items (CI)?
Does it require
release
management to package the
changes for successful deployment with minimal disruption to production?
Is change
and configuration management software identified in the
approved enterprise information management technology list?
Does the methodology include change
assessment?
Does the methodology include change
communication management?
Does it address change
database management and change information management?
Does the methodology include change
information management
systems?
Does change management scope include change
information management technology?
Is change management
included in change IT management policy?
Are change
management activities clearly defined?
Is there provision for change
management and project management?
is change
management and quality assurance covered?
Is change
management and software development included in the methodology?
Are change
management best practices documented and communicated?
Is a change
management checklist available?
Is a change
management configuration baseline established?
What is the status of the change
management database?
Are change
management issues defined and understood?
Does the organization have change
management methodologies?
Does the methodology include change
management of business
requirements?
Are change
management phrases incorporated in a project management framework?
Is there a formal
requirement for a change management plan?
Is a change
management plan template available?
Is change
management planning part of the project management plans?
Are change
management plans created for all changes?
Are change
management policies established and followed?
Are industry standard change
management practices followed?
Are change
management procedures documented?
Is the change
management process clearly defined?
Is a change
management process model utilized?
Does the change management strategy
clearly define change
management processes and change management process steps?
Do
change management projects and change management project management
specify requirements for a change management project plan?
Does the methodology include
process steps for change management quality
assurance?
Is a change
management review included in the methodology?
Is change
management risk adequately covered in the methodology?
Are change
management tools identified in the approved enterprise information
management technology list?
Are change
request management processes defined?
Is change
request project management included in the methodology?
Does the change management
guide include communication and change
management?
Are
configuration change management and configuration identification change
management processes documented?
Is documentation
change management included in the change management guide?
Is enterprise
software change management covered?
Is the importance
of change management communicated to all project team members?
Is an IT change management policy established?
Is project
change management defined in project management plans?
Does the change management
guide address release management?
Do project requirements
management plans address requirements change
management and the requirements change management process?
Are risks
associated with change management well documented and understood?
Is security
change management addressed as part of security policy or change
management policy?
Summary...
A change management strategy and methodology
provide
a disciplined process for
introducing changes into the production environment with minimal
disruption to ongoing operations.
This is a critical component of
successful information
management and it is important to gain a good understanding of the "as
is" situation to determine what changes might be required.
|
