GSOE9820 · Engineering Project Management
Project Integration and Change Management
Integration (CLO 4) is the central idea of the course: the end-to-end mapping between plan parts — risk based on the real scope and stakeholders, budget consistent with schedule, benefits mapped to stakeholders — with few loose ends. It is examined through Task 3, where teams receive a change request (budget, scope or risk) and must re-integrate the whole PMP, then justify it live in the 20% interview, making this chapter the hinge between planning and assessment.
What this chapter covers
- 01The Project Management Plan as the integrated master document (baselines + subsidiary plans)
- 02Project integration: mapping details between plan parts so budget↔schedule↔risk↔scope stay consistent
- 03Justification as a proxy for integration — a well-integrated plan is easy to defend
- 04The three content types per subsidiary plan: baselines, methods (and why chosen), and plans for the executing PM
- 05Integrated change control: assess every change across scope, schedule, cost and risk before approval
- 06Propagating a change request through scope → WBS → schedule → budget → risk register → benefits
- 07Baselines updated only through formal change control; guarding against scope creep
Propagate a change request through the plan
- +1Assess the change first (integrated change control). Before approving, evaluate the dashboard's impact across all four dimensions — scope, schedule, cost and risk — rather than treating it as a local add-on. Approved changes will update the baselines.
- +1Propagate to scope and schedule. Add the dashboard deliverable to the scope statement and a new branch to the WBS (nouns, still 100%); create its activities and insert them into the network. Because the deadline is fixed, check whether the new work lands on or lengthens the critical path — if so, the schedule must be compressed (crash/fast-track) elsewhere.
- +1Propagate to cost and risk. Add the dashboard's cost to the affected work packages and re-aggregate the cost baseline; if the fixed deadline forces crashing, add those costs too and check the contingency reserve. Add new risks (e.g. data-integration failure) to the register with triggers, responses and costed contingency.
- +1Re-check benefits and integration. Map the dashboard's benefit to the stakeholders who receive it and confirm it advances the strategy. The completeness check is that no loose ends remain — the change appears consistently in scope, WBS, schedule, budget, risk and benefits — and that you can justify the re-integrated plan to the sponsor.
Key terms
- Project Management Plan (PMP)
- The master document that integrates all subsidiary management plans and the scope/schedule/cost baselines, describing how the project is executed, monitored, controlled and closed.
- Project integration (CLO 4)
- The end-to-end mapping of details between plan parts so that risk reflects the real scope and stakeholders, budget and schedule are consistent, and benefits map to stakeholders — with few loose ends. The central idea of the course.
- Justification
- Defending how an integrated plan delivers the project robustly. How easily a plan can be justified is a proxy for how well integrated it is; the interview tests this directly.
- Baseline
- The approved version of the scope, schedule or cost plan against which performance is measured; changed only through formal change control.
- Integrated change control
- The process of assessing every proposed change for its impact across scope, schedule, cost and risk before approval, and updating the baselines when it is approved — the execution-phase face of integration.
- Scope creep
- Uncontrolled growth of scope without corresponding changes to time, cost and resources; prevented by controlling scope and routing all changes through integrated change control.
Project Integration and Change Management FAQ
What does integration actually mean in this course?
It is the end-to-end consistency of the plan: the risk register reflects the real scope and stakeholders, the budget matches the schedule, contingencies trace to risks, and benefits map to stakeholders — with few loose ends. CLO 4 makes integration (and being able to justify it) the central marked idea, so a plan that looks tidy but cannot be executed usually fails on integration, not on the individual methods.
How does a change request get handled?
Through integrated change control: assess the change's impact across scope, schedule, cost and risk before approving it, then, if approved, propagate it through every plan part (scope → WBS → schedule → budget → risk → benefits) and update the baselines. A change is never a local edit; the whole plan must stay consistent.
What is Task 3 and how does it feed the interview?
After Task 2, the team receives a tailored change request (a budget change, a scope change, or new assumptions/risks) and must re-integrate the PMP around it. Task 3 is not separately weighted — it is the basis of the individual interview (20%), where you are asked what you changed, how it rippled through the plan and how it affected the risk profile.
How do I show a plan is well integrated?
By being able to justify it: trace each contingency to its budget line, each task to its deliverable, each risk response through scope, schedule and budget, and each benefit to a stakeholder. If you can defend the whole chain to a sponsor with nothing dangling, the plan is integrated; if a part contradicts another, it is not.
Exam move
Treat integration as the thread that ties the whole course together and practise it as a propagation drill: take a single change (add a deliverable, cut the budget, tighten a deadline) and trace it through scope → WBS → schedule → cost baseline → risk register → benefits, checking the critical path and reserves as you go. The completeness test is "no loose ends": if any plan part still reads as if the change never happened, keep going. Rehearse justification out loud, because the interview is where integration is graded — be ready to trace a contingency to its budget line, a task to its deliverable, and a risk response through the plan, and to say how a change altered the risk profile. Understand the three content types each subsidiary plan should show (baselines, methods and why chosen, plans for the executing PM) so your PMP demonstrates integration rather than just compiling documents. Keep the integrated-change-control steps ready for quiz recall. Ask Sia to hand you a change request and check whether your propagation and justification hold together.
Working through Project Integration and Change Management in GSOE9820? Sia is AskSia’s AI Business and Economics tutor — ask any GSOE9820 Project Integration and Change Management question and get a clear, step-by-step explanation grounded in how GSOE9820 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
