This Scope Management Plan example shows how Alex Morgan, PMP, defined the complete approach for managing scope throughout Project Phoenix — a $72,250 website launch managed using the PMBOK Guide 8th Edition. From requirements collection through WBS creation, formal validation, and change control, this plan was the governance backbone that kept the project's scope clean from kickoff to closure.

What Is a Scope Management Plan?

A Scope Management Plan is a subsidiary component of the Project Management Plan that describes how the project scope will be defined, developed, monitored, controlled, and validated. It covers the approach to requirements collection, the method for developing the WBS, the process for validating completed deliverables against acceptance criteria, and the procedures for controlling scope changes. In PMBOK 8, scope management is addressed within the Planning and Delivery Performance Domains. A well-written Scope Management Plan prevents the two most common scope failures: scope creep (uncontrolled additions that inflate cost and schedule) and scope gap (missing requirements that are discovered late, causing rework).

What's Inside This Scope Management Plan Example

This Scope Management Plan example for Project Phoenix includes:

• Requirements collection approach: stakeholder interviews (8 participants, March 11), facilitated requirements workshop (March 12), and post-workshop stakeholder survey to validate priority and completeness before scope is finalized
• Scope definition process: requirements mapped to WBS work packages through a structured decomposition workshop; WBS reviewed and approved by Alex Morgan and Riley Park before baseline approval on March 17
• WBS approach: traditional WBS (deliverable-based decomposition to Level 2), not a backlog — aligned with the project's Predictive development approach; four agile sprints within the Development WBS package
• Scope validation: formal UAT reviews at two milestone gates — Sprint 3 review (April 30) for design and frontend deliverables, Sprint 5 review (May 30) for full-system acceptance including backend, CRM, and performance testing
• Scope control: all scope change requests processed through the CCB — CR form submitted, impact analysis completed within 48 hours, disposition documented and communicated to affected stakeholders; 2 CRs approved (CR-001, CR-002), 1 deferred (CR-003), 1 approved as minor technical change (CR-004)
• Scope creep prevention mechanisms: explicit out-of-scope list in the Scope Statement reviewed at every weekly status meeting; stakeholder reminder email sent at project midpoint confirming out-of-scope items

How Alex Morgan Used This Scope Management Plan

The Scope Management Plan's out-of-scope review mechanism — a standing agenda item in every weekly status meeting — was one of the most effective anti-scope-creep tools on Project Phoenix. By reviewing the out-of-scope list every week, Alex Morgan kept the boundaries fresh in every stakeholder's mind. When MCG's Marketing Director raised the idea of adding a resource library during Week 7, she prefaced it with "I know this is probably out of scope, but..." — exactly the response that the weekly review protocol was designed to produce. The library was logged as a Phase 2 requirement and did not disrupt the project. The Scope Management Plan created a culture of scope awareness, not just a set of rules.

Download and Customize

This Scope Management Plan example is available as a free download. Use it as a reference to build your own plan, or start with the blank template and fill it in for your project.

• Download the Scope Management Plan Template — PMBOK 8 (blank, ready to use)
• Read the article: Scope Management Plan in PMBOK 8 — Guide and Best Practices

Scope Management Plan Example: Key Takeaways

The most important lesson from this Scope Management Plan example is that scope control is most effective when it is proactive rather than reactive. Alex Morgan did not wait for a scope change request to be submitted before reminding stakeholders of the project boundaries — she proactively reviewed the out-of-scope list every week, creating an environment where stakeholders self-regulated their own requests. Combined with a fast (48-hour) change request turnaround for formal submissions, this approach meant that scope was never a source of tension or frustration. Stakeholders felt heard because their ideas were documented and deferred to Phase 2 — not dismissed.

Want to go deeper? The PMBOK Guide 8th Edition is the definitive reference for modern project management. Get your copy and use it alongside these examples to build a solid, practical understanding of every performance domain.