PMGT1860 · Project Initiation and Scope
Managing Scope & the Project Charter
Week 5 is the heart of the unit: writing a usable scope statement, recognising and controlling scope creep, and assembling the Project Charter — the document that formally authorises a project — with its twelve components and a milestone schedule carrying acceptance criteria. The scope statement and charter are the backbone of the group Comprehensive Project Initiation Plan, and change-control and charter-component questions are quiz staples.
What this chapter covers
- 01Project scope — the boundaries: deliverables, size, timing and cost (what is and is not included)
- 02The six-element scope statement — purpose/problem, deliverables, in-scope, out-of-scope, assumptions & constraints, success criteria
- 03Scope creep — uncontrolled growth without adjusting time, budget or resources (~52% of projects, PMI 2023)
- 04Protecting scope — get it in writing, formal change control (document → evaluate → approve/reject), milestone reviews, sign-off
- 05Change Control Board (CCB) and the change request as the way to say 'no' safely
- 06Project Charter — the deliverable that formally authorises the project and grants the right to detailed planning
- 07The twelve charter components — title, scope statement, business case, in/out-of-scope, milestones, stakeholders, constraints, assumptions, risks, budget, success criteria, signatures
- 08Milestone schedule with acceptance criteria — milestone, completion, responsible stakeholder, acceptance signal
Applied: diagnose the failure and attribute the charter components
- +1(a) The failure is scope creep — uncontrolled additions (whole city, helicopter DJ) without adjusting the time, budget or resources, so a fixed $5,000 is silently overrun.
- +1(b) The control is formal change control: every scope change must be documented, evaluated, then approved or rejected (a Change Control Board is the chartered approving body). Get scope in writing, hold milestone scope reviews, and get stakeholder sign-off.
- +1Instead of a silent 'yes', respond with a change request — 'that's a great idea; let's raise a change request' — which forces the time/budget impact to be seen before the change is accepted.
- +1(c) The scope statement belongs in the charter (component 2), the business case belongs in it (component 3), and the signatures belong in it (component 12).
- +1A fully detailed week-by-week schedule does NOT belong in the charter — the charter is a high-level authorising document that carries a milestone schedule, not a detailed plan. Detailed scheduling comes later in planning. The rule: if it's not in the charter, it's not in the project, and all scope changes must be agreed, documented and signed.
Key terms
- Scope statement
- A usable definition of the project's boundaries carrying six elements: purpose/problem, major deliverables, in-scope work, out-of-scope items, key assumptions and constraints, and success/acceptance criteria.
- Scope creep
- The uncontrolled expansion or growth of a project's scope without adjustments to time, cost and resources (PMBOK). Often starts small and accumulates into large overruns; PMI (2023) reports about 52% of projects experience it.
- Change control
- The formal process by which every scope change is documented, evaluated and approved or rejected against the baseline. A Change Control Board (CCB) is the formally chartered body that approves or rejects changes.
- Project Charter
- The document that formally authorises a project and grants the team the right to proceed to detailed planning. The sponsor owns it; the PM and team usually develop it. It sets boundaries but does not eliminate risk or replace stakeholder engagement.
- Charter components (twelve)
- Project title; scope statement; business case; in/out-of-scope activities; milestones (and WBS); stakeholders; constraints; assumptions; project risks; estimated budget; success criteria; signatures.
- Milestone schedule with acceptance criteria
- A summary-level schedule of major milestones, each with a completion point, a responsible stakeholder and a verifiable acceptance criterion — not a detailed activity schedule.
Managing Scope & the Project Charter FAQ
What exactly does a scope statement need to contain?
Six things: the project purpose or problem, the major deliverables, the in-scope work, the out-of-scope items, the key assumptions and constraints, and the success or acceptance criteria. Naming what is out of scope is as important as what is in — it draws the boundary that protects the project from scope creep later.
What is scope creep and how do you stop it?
Scope creep is uncontrolled growth in scope without adjusting time, budget or resources — it usually starts as small 'can you just add…' requests that accumulate into an overrun (PMI reports about 52% of projects experience it). You stop it by getting scope in writing, running every change through formal change control (document → evaluate → approve or reject), holding scope reviews at milestones and getting stakeholder sign-off, and answering new asks with a change request rather than a silent yes.
What is the Project Charter actually for, and who owns it?
The charter formally authorises the project — it is the official written acknowledgment that a project exists and grants the team the right to move to detailed planning. It defines objectives, high-level scope, assumptions, constraints and key stakeholders. The sponsor owns the charter, though the PM and team usually develop it, and it must be agreed by all key stakeholders before the project starts. It is not a detailed plan and does not eliminate risk.
How central is the charter to the group assessment?
Very. The group Comprehensive Project Initiation Plan is essentially a charter built out — scope statement, stakeholders, milestones, constraints, assumptions, risks, budget and success criteria. Knowing the twelve components and being able to draft a milestone schedule with acceptance criteria is what turns a vague pitch into a credible initiation plan. Confirm the group brief's exact requirements on Canvas.
Assessment move
This is the highest-leverage week for the group assessment, so build the artefacts, don't just read about them. Write a six-element scope statement for a project you know, explicitly listing out-of-scope items. Practise diagnosing a scope-creep scenario and prescribing change control. Memorise the twelve charter components — title, scope statement, business case, in/out-of-scope, milestones, stakeholders, constraints, assumptions, risks, budget, success criteria, signatures — and draft a short milestone schedule where each milestone has an owner and a verifiable acceptance criterion. Add a journal line on a scope decision you have seen, and confirm the group brief on Canvas.
Working through Managing Scope & the Project Charter in PMGT1860? Sia is AskSia’s AI Project Management tutor — ask any PMGT1860 Managing Scope & the Project Charter question and get a clear, step-by-step explanation grounded in how PMGT1860 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
