The 10 areas of knowledge. 1: Project integration management

A project without integration is a disconnected list of tasks. Each department pulls in its own direction, changes are applied without control, and in the end nobody knows whether the result delivers what was promised. That’s why the PMBOK places integration management as the first of its 10 knowledge areas: it’s what turns loose parts into a coherent whole.

According to the PMBOK (Project Management Body of Knowledge), a knowledge area is a field of project management defined by its requirements, processes, practices, tools, and techniques. All PMBOK processes are distributed across these 10 areas:

1. Project integration
2. Scope management
3. Time management
4. Cost management
5. Quality management
6. Human resource management
7. Communications management
8. Risk management
9. Procurement management
10. Stakeholder management

In this article we focus on the first: integration.

What is integration management?

Integration management brings together the processes and activities needed for the project to exist beyond its parts. Without it, the project is merely a value proposition with a goal. Once its components are identified, defined, and integrated around the desired scope, the project is sufficiently defined to be accepted.

A common mistake is thinking that integration only happens at the start. In reality, it must be maintained throughout the entire project life cycle, during which six management processes tied to this knowledge area unfold.

The 4 keys to mastering integration are:

• Gain stakeholder acceptance from the outset
• Create a clear execution plan shared by all
• Manage changes with rigor and flexibility
• Close by learning from both mistakes and successes

1. Gain acceptance

Integration management will only be effective if you have the support of team members and, above all, stakeholders. Securing their acceptance from the start ensures the backing and funding needed for success.

Two key documents make this possible:

• Project charter — formally initiates the project, authorizes the project manager to organize resources, and defines roles and responsibilities.
• Preliminary scope statement — establishes the reasons for the project, objectives, detected constraints, possible solutions, and identifies key stakeholders. It also defines the tactics for change control.

With these two documents you can guarantee that resources are coordinated and scheduled in the right form and at the right time.

2. Create an execution plan

The next step is to identify the activities needed to effectively execute, manage, and monitor the project. This is where a project management tool becomes essential — one that lets you plan and supervise at any time, from anywhere.

A Gantt chart lets you visualize project tasks and assigned resources while providing daily status updates. As the project progresses, it’s critical that every team member updates the completion status of their tasks so that reports reflect reality.

Integration is not a one-time event — it’s a continuous process that requires constant visibility into the project’s real status.

3. Manage changes

One of the biggest challenges is people management. Interests from different departments can overlap, and change requests will come more than once.

Being effective doesn’t mean accepting everything — it means being willing to make controlled concessions. Above any request sits the need to meet the project’s objectives and requirements.

To maintain control:

• Monitor work by measuring and balancing actual progress against the plan.
• Apply corrective or preventive actions when needed.
• Follow the change control process defined in the scope statement.
• Ensure every change request goes through proper channels before becoming part of the plan.
• Evaluate each change individually: only validated and approved changes get implemented.

4. Close by learning

At the end of the project, verify that all activities are complete and that the final product or service meets client and stakeholder expectations. It’s advisable to obtain written approval of the closure.

Then comes the most valuable part: learning. A formal lessons-learned session with the team allows you to identify:

Dimension	Key question
Weaknesses	What failed internally?
Threats	What external factors affected us?
Strengths	What did we do well as a team?
Opportunities	What could we have leveraged better?

Everything learned feeds into the next project — where the team will inevitably be more effective.

Next steps

• Try ITM Platform for free — integrate activities, resources, costs, and risks in a single tool.
• Browse project management resources — e-books, guides, and templates for your PMO.