Project Management guide · Risk, quality and control
Project Integration Management: Processes and Examples
Project integration management is the work of coordinating every part of a project so that scope, schedule, cost, quality, risk, resources and stakeholders pull in the same direction. It is the project manager's core job: making trade-offs, joining up plans and keeping the whole project aligned with its objectives.
Key takeaways
- Integration management makes all parts of a project work together.
- It is the project manager's core and non-delegable responsibility.
- Assess every change across scope, schedule, cost, quality, risk and resources.
- It runs from the charter right through to formal closure.
What integration management means
Most project management activities focus on one area, such as the schedule or the budget. Integration management looks across all of them. A decision in one area almost always affects another: adding scope changes cost and time, cutting testing raises quality risk, and moving a milestone changes resource plans. Integration is how the project manager sees those links and makes balanced decisions.
- Unify: combine subsidiary plans into a single project management plan.
- Coordinate: make sure teams, suppliers and workstreams hand work to each other smoothly.
- Decide: weigh competing objectives and agree trade-offs with the sponsor.
- Control: track performance against the baseline and manage changes as one system.
The seven integration processes (PMBOK Guide, 6th edition)
The sixth edition of the PMBOK Guide groups integration management into seven processes. The seventh edition moved to principles and performance domains, but these processes remain a useful map of the work.
| Process | Process group | Main output |
|---|---|---|
| Develop project charter | Initiating | Project charter |
| Develop project management plan | Planning | Project management plan |
| Direct and manage project work | Executing | Deliverables, work performance data, issue log |
| Manage project knowledge | Executing | Lessons learned register |
| Monitor and control project work | Monitoring and controlling | Work performance reports, change requests |
| Perform integrated change control | Monitoring and controlling | Approved or rejected change requests, change log |
| Close project or phase | Closing | Final report, transitioned deliverables, archived records |
How to manage integration in practice
- Start with a clear charter: agree purpose, objectives, high-level scope and authority so later decisions have a reference point.
- Build one integrated plan: link scope, schedule, cost, risk, quality, resource and communication plans so they use the same assumptions and dates.
- Set baselines: fix scope, schedule and cost baselines once the plan is approved.
- Run a regular control cycle: compare progress with the baselines, for example using earned value, and report through a status report.
- Route all changes through one process: use change control so every change is assessed for its effect on all areas, not just one.
- Capture knowledge as you go: keep a lessons learned register throughout, not only at the end.
- Close formally: hand over, release resources and archive records through project closure.
Worked example: an integrated trade-off
A website rebuild has a budget of $200,000 and a launch date of 1 March. In week 10 the marketing team asks for a new product configurator. The project manager assesses the request across every area before taking it to the change board.
| Area | Impact of adding the configurator |
|---|---|
| Scope | One new feature, about 120 hours of design, build and test |
| Schedule | Launch moves 3 weeks later unless work is re-sequenced |
| Cost | About $14,000 in extra developer time |
| Quality | Testing window shrinks if the date is held |
| Risk | New integration with the pricing system, rated high |
| Resources | Lead developer already at full capacity |
| Stakeholders | Sales strongly in favour; finance concerned about cost |
The board considers three options: add it now and move launch, hold the date and drop a lower-value feature, or launch on time and add the configurator in a second release. It chooses the third option. Scope, schedule and cost baselines stay intact, and the configurator becomes a separate change with its own budget. This is integration management at work: one decision, assessed across every area.
Integration in Agile projects
In Agile teams much of the detailed integration happens inside the team. The product owner balances scope and value through the backlog, and short iterations keep plans and delivery aligned. The project manager or delivery lead still integrates at a higher level: funding, dependencies between teams, governance, release planning and stakeholder communication.
Common mistakes
- Treating plans as separate documents that never reference each other.
- Approving changes based on cost alone without checking schedule, risk and quality.
- Letting workstreams report in different formats, so nobody sees the whole picture.
- Leaving lessons learned and closure until the very end.
- Confusing integration with doing everything personally. The project manager coordinates; specialists still own their areas.
Free templates for this topic
Frequently asked questions
What is project integration management?
It is the coordination of all project management areas and activities so that the project works as one system and meets its objectives.
Why is integration management important?
Because decisions in one area affect others. Without integration, teams optimise their own part and the project as a whole suffers.
Who is responsible for project integration management?
The project manager. Others contribute, but accountability for integrating the project sits with the project manager.
How many processes are in integration management?
The PMBOK Guide sixth edition lists seven, from developing the charter to closing the project or phase.
What is the first process in integration management?
Develop project charter, which formally authorises the project.
What is integrated change control in integration management?
A single process for reviewing every change request and assessing its effect on scope, schedule, cost, quality, risk and other areas before deciding.
What is the difference between integration management and scope management?
Scope management defines and controls what work is included. Integration management coordinates scope with every other area.
Is integration management on the PMP exam?
Integration topics such as planning, change control and closure appear throughout the exam, which is now organised by domains rather than knowledge areas.
Does PMBOK 7 still include integration management?
The seventh edition is organised around principles and performance domains rather than knowledge areas, but integration remains central to the project manager's role.
What documents support integration management?
The project charter, project management plan, baselines, change log, issue log, lessons learned register and final report.
How does integration management work in Agile?
Teams integrate continuously through the backlog and short iterations, while a delivery lead handles cross-team dependencies, funding and governance.