Project Change Management
Intend of this process is to track and control the changes and defects requested in Configuration Items throughout the project life cycle. Sources of changes and defects can be internal or external.
Changes can be raised internally by the project team as the project evolves and requirements get refined in later phases. Externally, though the customer can request a change at any stage of the project changes and defects after project delivery is a major source of initiating change management process.
Change Management Process Diagram
| Role | Activity | Artifacts/templates | ||
| Requester |  | Log Changes/Defects | | Issue List |
 | ||||
| Configuration Control Board | | Perform Impact Analysis | | Issue List |
| ||||
| Configuration Control Board | | Assign for Implementation | | Issue List |
| ||||
| Assigned Role | | Update Effected Artifacts | | Updated Artifacts |
| ||||
| Assigned Role | | Update Revision History of Effected Artifacts | | Revision History of Updated Artifacts |
| ||||
| Assigned Role | | Review Updated Artifacts | | Review Comments Revision History |
| ||||
| Assigned Role | | Approve Artifacts | | Approved Artifacts |
| ||||
| Project Manager | | Update Change/Defect Status | | Issue List |