8 Project Integration, Evaluation, and Learning

Integrating project plans

A project’s scope, schedule, budget, resources, quality standards, risks, stakeholder needs, and communications are interdependent. Integration management coordinates these elements so decisions support the project’s overall objectives rather than optimizing one area at another’s expense. For example, adding a feature may affect scope, delivery date, cost, staffing, testing, and user training.

The Project management plan brings supporting plans together and establishes approved baselines for scope, schedule, and cost. The team uses these reference points to guide work and judge performance. A baseline should not be changed informally: proposed changes must be documented, assessed for effects across the project, and approved by the appropriate decision-maker before the plan and related records are updated. This is integrated change control.

Monitoring and controlling performance

Monitoring and control is a recurring process: collect reliable information about project work, compare actual progress with the plan, identify variances and emerging risks, and decide whether action is needed. Useful reports show current status and trends, such as whether milestone delays are increasing or costs are rising faster than planned.

Performance measures should match project objectives. A team might track milestone completion, spending, defects, unresolved risks, and stakeholder acceptance. A variance is a signal to investigate, not automatically proof of failure. The team should identify its cause, forecast its likely effect, and communicate the implications to relevant stakeholders.

Monitoring can prompt corrective action to bring performance back in line or preventive action to reduce the chance of a future problem. If a response requires a baseline change, it must follow the agreed approval process.

For example, a reporting-system project is two weeks behind because data from a supplier arrived late. The project manager updates the forecast, assesses effects on testing and cost, and informs the sponsor. The team evaluates options, such as resequencing independent tasks, without silently changing the agreed delivery target. If a revised target is necessary, the team submits a change request with its impacts and recommendation.

Managing changes

A sound change process clarifies how requests are raised, who evaluates them, who can approve them, and how approved decisions are communicated. Evaluation considers effects on requirements, scope, schedule, budget, quality, resources, risks, operations, and expected benefits. A decision may approve or reject the request, defer it, or ask for more information. After approval, the team updates relevant plans and records and tells affected people what has changed.

Agile teams also manage change deliberately. They can adapt the order and content of future work as they learn, while keeping priorities visible and regularly reviewing progress with stakeholders. Frequent delivery and feedback help teams respond to change without losing sight of customer value.

Evaluating outcomes and benefits

Project evaluation compares results with objectives and acceptance criteria, examines the quality and usefulness of deliverables, and considers whether the work produced intended outcomes and benefits. A deliverable is what the project creates; an outcome is the change that results when people use it; a benefit is the value that change provides.

For example, a project may deliver a new online application form on schedule. Applicants may then complete submissions more easily, reducing processing time. The project team can verify delivery and initial acceptance at closeout, while a designated operational owner may need to measure longer-term benefits after the project ends. Defining measures, owners, and review timing helps make that follow-up possible.

A balanced evaluation reviews planned versus actual scope, time, cost, and quality; explains major variances and approved changes; records stakeholder feedback; and considers whether benefits are likely to be sustained. Conclusions should be evidence-based: a project can meet its delivery targets yet fall short of intended value, or deliver lasting value despite reasonable changes to its original plan.

Capturing lessons and closing the project

Lessons learned are practical observations that can improve current or future work. Capture them throughout the project, while the context is still clear. Record what happened, why it happened, its effect, and what action or practice should be repeated or changed. Include successes as well as problems, and identify useful causes and responses rather than assigning blame.

At closure, confirm that deliverables have been accepted, remaining responsibilities have been handed over, records are complete, and project results and lessons are shared with appropriate people. Lessons have lasting value when they are easy for others to find and are applied to future planning, decisions, or working practices.