GAQM APM study materials
GAQM APM study resources

GAQM APM: Project Initiation and Scope Definition

GAQM APM · Work through your exam, one topic at a time.

All guide sections

Project Initiation and Scope Definition

What this domain tests

This domain tests how a business need becomes an authorized, bounded project. Expect questions on the charter, stakeholder identification, requirements, scope statement, WBS, and the scope baseline. The exam favors scenarios that ask what document authorizes work or what belongs in the baseline.

Initiation

  • The business case explains why the project is worth doing; it is not the same as the charter.
  • The project charter authorizes the project and the project manager, and records high-level scope, success criteria, assumptions, constraints, budget, milestones, and sponsor authority.
  • The stakeholder register identifies stakeholders and records analysis and engagement strategy; it is a living document.

Scope definition and baseline

  • Requirements are elicited, documented, and traced so that deliverables can be verified.
  • The scope statement defines what is in and out of scope, acceptance criteria, exclusions, assumptions, and constraints.
  • The WBS decomposes deliverables into work packages; it is deliverable-oriented, not an org chart. The 100% rule means the WBS covers all project scope and no more.
  • The WBS dictionary describes each work package. Scope statement + WBS + WBS dictionary form the scope baseline.
  • Verify Scope obtains formal acceptance of completed deliverables; Control Scope monitors status and manages changes.

Worked example

A sales vice president asks the team to add a mobile dashboard to a reporting project. The project manager checks the charter and scope statement: the dashboard is not listed. She logs the request as a change, estimates cost and schedule impact, and sends it to the change control board. Reasoning: a verbal request is still a potential change; the baseline cannot be altered without integrated change control. If approved, the scope statement, WBS, and baseline are updated.

Traps

  • Confusing the charter with the scope statement or the business case.
  • Treating the WBS as a task list or organization chart.
  • Allowing scope creep by accepting informal additions.
  • Confusing gold plating (extra features) with scope creep (uncontrolled additions).
  • Forgetting exclusions; they prevent later disputes.