PMGT5820 Chap.1 Project Start-Up and Scope Baselines
Project Start-Up and Scope Baselines
Project execution becomes controllable only after the team shares an authorised reference. This chapter connects sponsor purpose, kick-off alignment, scope boundaries, deliverables, the work breakdown structure, schedule and cost expectations, and acceptance criteria. The central skill is tracing each work package back to an agreed result and preserving that baseline until delegated authority approves a change.
Start-up is therefore more than a meeting or document bundle. It is the point at which assumptions become visible, decision rights are named and the team agrees how progress will be compared with commitment. A useful baseline integrates scope, time and cost rather than letting three files describe different projects. It also identifies exclusions, interfaces and acceptance evidence early enough to expose ambiguity.
When execution later produces a request, defect or forecast change, this shared reference lets the manager classify the condition, analyse consequences and route a decision without erasing the history that made the variance meaningful.
What this chapter covers
- 01
Kick-off meetings as alignment and control interventions
- 02
Scope statements with inclusions, exclusions, assumptions and constraints
- 03
Deliverables versus the activities used to create them
- 04
Work breakdown structures, ownership and dependency logic
- 05
Integrated scope, schedule and cost baselines
- 06
Acceptance criteria and delegated approval authority
Worked example · free
Repair an unready project baseline
- +1Translate the purpose into observable deliverables and acceptance conditions.
- +1Record exclusions, assumptions and constraints so later change can be classified.
- +1Decompose deliverables into owned and estimable work packages.
- +1Link dates, resources and cost expectations, then check dependencies.
- +1Obtain approval from the delegated authority and preserve the authorised version.
Key terms
- Scope statement
- The documented boundary of deliverables, exclusions, assumptions and constraints.
- Work package
- A manageable part of the work breakdown structure that can be owned, estimated and controlled.
- Baseline approval
- Formal authorisation of the project reference used for later comparison.
- Acceptance authority
- The delegated role permitted to confirm that a deliverable meets agreed criteria.
Project Start-Up and Scope Baselines FAQ
When is a project plan ready to become a baseline?
It is ready when deliverables and exclusions are clear, work packages have owners, dependencies and resources are coherent, acceptance criteria are observable, and the correct authority approves the integrated scope, schedule and cost reference. A saved schedule without that authority is still a working plan.
How can I tell clarification from scope change?
Trace the request to the approved requirement, exclusion, assumption and acceptance criteria. A clarification makes an existing commitment precise. A scope change adds, removes or alters a committed result or constraint and therefore needs impact analysis and delegated approval.
Why does acceptance belong in start-up planning?
Acceptance criteria define how the client will recognise a satisfactory result. Writing them early exposes ambiguous requirements, assigns verification responsibility and prevents the team from declaring completion based only on activities finished rather than outcomes accepted.
Assessment move
Draw one traceability chain from sponsor purpose to deliverable, work package, milestone and acceptance evidence. Then challenge it with a new request and decide whether it is clarification, defect correction or change. Practise naming the approval role and every linked artefact that must update after an authorised change. Begin revision with a blank page rather than a completed template.
Write the intended project outcome, then identify the smallest observable deliverables that collectively create it. Add exclusions and assumptions beside the relevant deliverable so they cannot disappear into a general notes section. Decompose one deliverable into work packages and test each package for a single accountable owner, a measurable completion condition and a clear connection to schedule and cost.
Next, draw dependencies and ask what evidence justifies each duration or resource estimate. Compare the resulting plan with the acceptance criteria: if completion can be claimed without producing the evidence the client needs, the chain is incomplete. Use a second pass to identify authority. Mark who can approve the original baseline, who can recommend movement and who merely supplies information.
Rehearse three short scenarios: an unclear requirement, an output that fails the approved requirement and a stakeholder request for new capability. For each, state the classification, immediate record, impact analysis and decision route. Finish with a baseline audit in which scope, schedule, cost, risk and acceptance records all describe the same version.
This method prepares both written baseline work and timed explanations because it turns a large planning topic into a sequence of traceable decisions. Review the chain aloud and correct any step whose evidence or owner cannot be named without consulting a generic label.
Working through Project Start-Up and Scope Baselines in PMGT5820? Sia is AskSia’s AI Project Management tutor — ask any PMGT5820 Project Start-Up and Scope Baselines question and get a clear, step-by-step explanation grounded in how PMGT5820 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
