Change Management

A critical component of project monitoring and control is change management. As business requirements and operating environments change all the time, the project manager has to manage change throughout the software development cycle from acquisition, supply, development, operation, and then maintenance. The guiding principles, techniques, and tools for change management are discussed in this chapter.

Application Change Management

Documentation Change Management

Documentation changes should be identified by a change table of contents at the beginning of each document. The change table of contents includes the effective date, affected sections of the document, and a summary of the change (see Figure 18-10). The purpose of the change table of contents is to summarize all changes for the reader.

Changes should be redlined in the text to identify the changed portion. If the old information is important, it may be moved to a footnote, dated, and labeled as a previous version. An example of this type of documentation change is shown in Figure 18-11. Keep in mind that you also keep the old version of the document for history.


Project # ___________________________
Project Name ______________________
CHANGE CONTROL IMPACT ASSESSMENT
						Date _________________
						Request # ___________

Impact of Change Request


Impact
Type	Cost	Person Days	Business Days	Budget Control
A.	_______	_______	_______	Initiation Date	____________
B.	_______	_______	_______	Request #	____________
C.	_______	_______	_______	Amount	____________
D.	_______	_______	_______	Approval Date	____________
E.	_______	_______	_______
F.	_______	_______	_______
Total	_______	_______	_______


STATUS		Scheduled Completion		Actual Completion
Initiated Date		__________		__________
Analysis Date		__________		__________
Development Date		__________		__________
Testing Date		__________		__________
Implementation Date		__________		__________

Comments:


Initiator		Date
Owner		Date		Project Manager			Date

FIGURE 18-5 Sample Change Request Impact Form


Project # ___________________________		Date _________________
Project Name _______________________		Request # _____________
PROJECT MANAGER CHANGE CONTROL CHECK LIST

DEVELOPMENT
		Required	Completion Date
1. QA/Documentation Review		______________	___________________
2. Update Source Document(s)		______________	___________________
3. Update Baseline Document(s)		______________	___________________
4. Update Program Specifications		______________	___________________
5. Revise Code		______________	___________________
6. Update User Documentation		______________	___________________
7. Update Operations Documentation		______________	___________________
8. Other: _______________________		______________	___________________
_____________________________

IMPLEMENTATION
		Required	Completion Date
1. Baseline Documents Update		______________	___________________
2. Requirement Change		______________	___________________
3. Design Changes		______________	___________________
4. Programming Changes		______________	___________________
Pgm #’s ____, ____, ____		______________	___________________
____, ____, ____		______________	___________________
5. Unit Testing		______________	___________________
6. System/Regression Testing		______________	___________________
7. Interface Changes		______________	___________________
8. Operations Changes		______________	___________________
9. Other: _______________________		______________	___________________
____________________________

Comments:
Initiator	Date
Owner	Date	Project Manager		Date

FIGURE 18-6 Project Manager's Change Check List

CHANGE CONTROL ANALYSIS BY TYPE PROJECT-TO-DATE Number and Cost of Change by Type
Application Name	#	A Cost	#	B Cost	#	C Cost	#	D Cost	#	E Cost	#	F Cost	#	G Cost	Total #	Cost
1. Branch Pilot	60	$.45.6	1	$ 2.6	--	--	--	--	3	$40.7	--	--	--	--	64	$ 88.9
2. Securities Transfer	17	--	--	--	2	--	--	--	--	--	--	--	--	--	19	--
3. Settlements	16	36.0	11	18.6	--	--	--	--	--	--	2	.5	--	--	29	55.1
4. Float allocation	--	--	3	6.0	16	$11.0	--	--	3	.4	1	$10.0	--	--	23	27.4
Total	93	$81.6	15	$27.2	18	$11.0	--	--	6	$41.1	3	$10.5	--	--	135	$171.4
Change Type Legend A. Requirements/Design B. Application Programs/Testing C. Documentation D. Hardware E. Purchased Software F. Interfaces G. Application Support Notes: Costs in thousands Changes with no cost are planned maintenance.

FIGURE 18-7 Summary Report of Change Costs

CHANGE CONTROL COST/SCHEDULE IMPACT* Month of May 1994
	Current Month		Year-to-Date		Project-to-Date
Application	Cost	Schedule	Cost	Schedule	Cost	Schedule
1. Branch Pilot	--	--	S 488	24	$ 88.9	39
2. Securities Transfer	$ 15.0	8	15.0	8	25.0	14
3. Settlements	111.0	64	111.0	64	2250	140
Total	$126.0	72	$174.8	96	$338.9	193
* All data based on Submission Date Cost in thousands Schedule in Business Days

FIGURE 18-8 Summary Report of Cost and Schedule Impacts

CHANGE CONTROL COST/SCHEDULE IMPACT* Month of May 1994
	Current Month						Year-to-Date						Project-to-Date
Project Name	S	P	A	D	O	C	S	P	A	D	O	C	S	P	A	D	O	C
1. Branch Pilot	--	--	--	--	--	--	6	1	4	1	1	3	64	1	51	12	25	26
2. Securities Transfer	3	1	2	--	1	1	22	1	18	3	6	12	22	1	18	3	6	12
3. Settlements	16	9	7	--	3	4	16	9	7	--	3	4	16	9	7	--	3	4
Total	19	10	9	--	4	5	42	11	29	4	10	19	102	11	76	15	34	42
LEGEND S Submitted P Pending A Approved D Disapproved/Cancelled O Open C Completed

FIGURE 18-9 Summary of Change Requests

CHANGE PAGE

Page No.	Reason for/description of change	Date
1-48	Original issue	11/4/93
AH	Audit review and Revisions	1/3/94
1-2.22	Corrections and revisions to reflect organization changes	2/6/94
6. 9, 37-44	Describe imaging interface	6/394

FIGURE 18-10 Sample Document Change Table of Contents