Introduction to NonStop Operations Management

Change and Configuration Management
Introduction to NonStop Operations Management–125507
7-12
Conclusion
Assign Knowledgeable Individuals With Responsibility for Change
Requests
Individuals with the most knowledge regarding the change request are chartered with the
responsibility of developing the needed plans. For example, installing a new version of
application software requires the applications development group to develop the test,
installation, backout, and verification plans. These plans are then presented at a change
control meeting for approval and scheduling.
Hold Periodic Change-Control Meetings
Periodic change-control meetings are now held with members from applications
development, technical support, quality assurance, computer operations, network
operations, and business operations. These meetings are chaired by the change
management group. The meetings focus on:
•
The previous week’s changes. The changes are reviewed and their status is noted.
•
New change requests. New changes are presented and reviewed. If all approval
criteria are met, the change is scheduled for installation.
The minutes of the meeting are published, and a weekly schedule is distributed to each
functional area and to management.
Conclusion
Definition of change management responsibility, formal change procedures, periodic
change-control meetings, and the development of a change schedule helps position
Allied Bank to manage more effectively the changes anticipated because of high growth.
Figure 7-1. Case Study: Change-Control Process Flow at Allied Bank
Development
Environment
Operations
Test
Environment
Customer
Production
Environment
Design
(new change)
Programming
System
Acceptance
Test
Librarian
Business Operations
Group
Technical Support
Group
Operations
Acceptance Test
Implementation
Production
Operations
Customer Acceptance
& Training
026