A change request formally proposes a modification to an approved requirement, product, process, or other work product.
The request describes the proposed change and its purpose. Moreover, it identifies the requester, affected items, priority, status, and target release.
First, the responsible team checks the request for completeness. Next, experts analyse its impact on requirements, costs, risks, schedules, architecture, implementation, tests, and documentation. Traceability links support this analysis. Therefore, the team can identify all affected artifacts.
A responsible authority then approves, rejects, or postpones the change request. For example, a Change Control Board may make this decision. The authority also records the decision and its reason.
After approval, the team prioritizes and implements the change. Finally, testers verify the result. The team then updates related artifacts, versions, and baselines.
A clear and traceable request supports informed decisions, controlled implementation, and consistent project results.
« Back to Glossary Index