Change Management
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
|
FIGURE 18-7 Summary Report of Change Costs
|
FIGURE 18-8 Summary Report of Cost and Schedule Impacts
|
FIGURE 18-9 Summary of Change Requests
CHANGE PAGE
|
FIGURE 18-10 Sample Document Change Table of Contents