Differentiate between scope statement and WBS.

Differentiate between scope statement and WBS.

• A. The scope statement defines boundaries and deliverables; the WBS decomposes the scope into work packages and activities.
• B. They are the same thing.
• C. The WBS defines boundaries and deliverables; the scope statement breaks work into packages.
• D. The scope statement is used for scheduling; the WBS is used for risk management.

Answer: (A)

Scope boundaries and deliverables are defined in the scope statement, while the WBS organizes the scope into work packages and activities. The scope statement tells you what’s in and out of the project, lays out objectives, major deliverables, acceptance criteria, constraints, and assumptions. The WBS, on the other hand, takes that defined scope and breaks it down into smaller, more manageable components—work packages that can be scheduled, estimated, and assigned. This decomposition provides a structure for planning, budgeting, and tracking progress. So the best choice reflects this separation: the scope statement sets the boundaries and deliverables, and the WBS decomposes the scope into work packages and activities. The idea that they’re the same thing, or that the WBS defines boundaries, or that the scope statement is mainly for scheduling (or risk management) doesn’t fit how these documents are used in project planning.

Scope boundaries and deliverables are defined in the scope statement, while the WBS organizes the scope into work packages and activities. The scope statement tells you what’s in and out of the project, lays out objectives, major deliverables, acceptance criteria, constraints, and assumptions. The WBS, on the other hand, takes that defined scope and breaks it down into smaller, more manageable components—work packages that can be scheduled, estimated, and assigned. This decomposition provides a structure for planning, budgeting, and tracking progress.

So the best choice reflects this separation: the scope statement sets the boundaries and deliverables, and the WBS decomposes the scope into work packages and activities. The idea that they’re the same thing, or that the WBS defines boundaries, or that the scope statement is mainly for scheduling (or risk management) doesn’t fit how these documents are used in project planning.