2 Project Scope and Requirements
Learn how project scope connects objectives, requirements, and deliverables; defines boundaries and acceptance; and provides a baseline for evaluating and managing change.
What project scope defines
Project scope describes the work a project will perform and the products or services it will deliver. A clear scope gives stakeholders a shared understanding, guides detailed planning, and helps determine whether proposed work belongs within the project.
A scope statement typically identifies major deliverables and exclusions, along with the boundaries of the work. Scope definition connects the project's —why it is being undertaken—to —what the result must do or satisfy—and deliverables—the outputs the team will produce. It should also make relevant constraints, assumptions, and interfaces clear.
Connect and
state the intended results. A broad objective such as “improve library access” is less concrete than “enable registered members to reserve available books online.” Where possible, should include measures of success and a target date or other relevant constraint.
express the capabilities, qualities, or conditions the project's product or service must meet. “The system shall let a registered member reserve an available book” is more verifiable than “The system should be easy to use.” Good are clear, necessary, consistent, and testable. Give them unique identifiers and link them to the objective or stakeholder need they support.
Plan how will be verified and maintain traceability between and their sources. This helps connect what the project must deliver to the needs and it is intended to address.
Define deliverables and acceptance
A is a defined output produced by the project, such as an approved design, working software feature, or training guide. State each clearly and specify how its completion or acceptance will be judged.
Acceptance criteria make expectations observable and reduce disagreement about whether work is complete. Connect them to relevant and agree them with the appropriate stakeholders. For example, an online reservation feature might be accepted when a member can reserve an available title, receive confirmation, and see the reservation in their account.
checks whether a meets its specified . checks whether the result meets the user's or customer's intended need. These checks address different questions: whether the specified are met, and whether the result serves the intended need.
Set boundaries and interfaces
Make the project's boundaries explicit so stakeholders can distinguish planned work from related work the project will not deliver.
In scope: work and capabilities the team will deliver.
Out of scope: related work the project will not deliver.
Interfaces: connections or handoffs with other systems, teams, or organizations.
Constraints and assumptions: limits the team must work within and conditions it is treating as true for planning.
For a library reservation project, online reservations may be in scope while redesigning the library's catalog system is explicitly out of scope. Naming exclusions and interfaces helps manage expectations and assess future requests against the agreed scope.
Use a to manage change
Once the relevant stakeholders approve the scope and , the team can use them as a for planning and evaluating proposed changes. The is a shared reference point for deciding how to respond when needs or conditions change; it does not make change impossible.
A basic change-control process is:
Record the requested change, its reason, and the or deliverables it affects.
Assess likely effects on scope, quality, cost, schedule, risks, and related work. Review requirement changes for effects on cost, schedule, design, and related .
Have the designated decision-maker or change authority approve, reject, or defer the request.
For an approved change, update , plans, acceptance criteria, and related records, and communicate the decision to affected stakeholders, including those who must implement or test it.
Verify the implemented change and close the request when the affected documentation and work are updated.
Assessing impacts before approval helps prevent unplanned work and makes trade-offs visible. Keep the approved and affected stakeholders up to date as changes are decided and implemented.