Change Request
DE: Aenderungsantrag
A formal proposal for a modification to a project document, deliverable, or baseline.
Detailed Explanation
A change request is a formal proposal to modify any document, deliverable, or baseline. They can originate from any stakeholder and may include corrective actions, preventive actions, defect repairs, or scope changes.
The integrated change control process ensures systematic evaluation. Each request documents what is changing, why, impact analysis covering all project dimensions, and the recommended action.
Not all change requests are scope additions — they can be scope reductions, process improvements, or risk responses. A healthy process balances stability with the reality that projects operate in dynamic environments.
Key Points
- Must go through formal change control process
- Can be corrective, preventive, or scope-related
- Requires documented impact analysis
- Can come from any stakeholder
- Approved changes update the project management plan
- Rejected changes should be documented with rationale
Practical Example
A client requests multi-language support mid-project. The PM documents: +3 weeks, +EUR 25K, architecture changes needed. The CCB approves with the condition that core features launch on time and multi-language follows as Phase 2.
Tips for Learning and Applying
Use a standardized change request form
Always include impact analysis before CCB submission
Track change requests in a log for trend analysis
Communicate approved changes to all affected stakeholders promptly
Want to Master These Concepts?
Our courses cover all these terms in depth with practical examples and exercises.