Defining in-scope and out-of-scope boundaries for an implementation
Key Takeaway
Scope is the boundary of an implementation, so write down what is out of scope as clearly as what is in scope.
Project scope is the boundary of an implementation. Scope covers all the work needed to deliver the expected outcome and states clearly what is included and what is not. Clear in-scope and out-of-scope boundaries keep the customer and the project team aligned. The same boundaries drive the schedule and cost estimates and protect the project from scope creep.
What project scope is
Project scope defines all the work that must be done to deliver the project's expected outcome. The scope describes precisely what is included and what is not included. The scope statement is the most fundamental deliverable on any project.
Scope comes from the requirements that the sponsor and key stakeholders provide. Scope planning is a joint effort between the project team and those key stakeholders. Together they define, discuss, and document the requirements. They must reach consensus on them. The requirements must be detailed enough that no one misunderstands what the project will deliver.
If the current business process is not well understood, analyze and document the current state before scoping. A gap analysis then describes the gaps between the current and intended processes.