Scope Management

A Scope Management Plan (SMP) provides a big-picture image, clearly defining what is and is not included in the project. Conway, Masters, and Thorold (2017) state that “the broader environment into which an innovation is born matters as much as the idea itself in determining whether sustainable innovation is achieved” (p. 26). Considering the project's purpose from a broad perspective, known as systems thinking, before creating the deliverables, helps ensure the innovation’s sustainability and the project’s success.

Click here to see the...

Scope Management tool

First, identify the project’s deliverables. Connect with stakeholders to clarify their expectations. Include intermediate and final deliverables, including documents, plans, schedules, and budgets. Ensure each is specific and verifiable.

Second, document all project requirements. This includes describing the characteristics of the final deliverable, including its functionality, creation and implementation, and any specific conditions that must be met. Requirements are measurable, testable, relate to the organization’s vision, and have sufficient detail such as its functional, non-functional, technical, user, and regulatory requirements (Watt, 2014, p.77).

Third, create a Work Breakdown Structure. Follow the “100 percent rule” (workbreakdownstructure.com, 2020) which breaks down the project’s deliverable-oriented work into increasingly smaller components. This makes it more manageable to schedule, estimate, and monitor time, cost and resource estimates.

Click here to see the...

Work Breakdown Structure tool

Finally, write a scope statement. This typically includes the project’s name, charter, project manager, stakeholders, problem statement, goals and objectives, deliverables, requirements, exclusions, milestones, and constraints. The scope statement clearly states what the project will produce and under what constraints and assumptions the project will work.