Study guides / CAPM: Certified Associate in Project Management / Integration & change
Integration & change
CAPM: Certified Associate in Project Management · quick review
How the project manager ties the pieces together: the charter that starts the project, the plan that guides it, and the change control that protects its baselines.
The rules
- The project charter authorizes the project and names the project manager. It records the purpose, high-level requirements, summary milestones and budget, key risks and the sponsor.
- The project management plan combines the subsidiary plans (scope, schedule, cost, quality, resources, communications, risk, procurement, stakeholder engagement) and the baselines (scope, schedule, cost; together the performance measurement baseline).
- Integrated change control: every change request is documented, analyzed for impact on scope, schedule, cost, quality and risk, then approved or rejected (often by a change control board). Approved changes update the plan and are communicated.
- Corrective actions, preventive actions and defect repairs can all be change requests.
- Key project documents: assumption log, issue log, change log, lessons learned register (kept throughout, not just at the end).
- Closing: confirm acceptance, transfer the deliverables, release resources, close contracts, finalize lessons learned and archive records.
Common traps
- A stakeholder asking a team member directly doesn't bypass change control; the request still goes through the process.
- Gold plating (adding extras nobody asked for) is uncontrolled change, even if it seems helpful.
- Lessons learned are gathered throughout the project, not only at closing.
How it's tested
"What should the project manager do first?" scenarios: usually evaluate the impact, follow the change process, and consult the plan.
Practise it
The full lesson, worked examples and practice questions are in Tickmark, where every answer choice is explained.
Open the full lesson