3 Scope and Requirements Management
Learn how to define project requirements and scope, organize authorized work into deliverables, and assess and control proposed changes.
Connect scope and requirements
describes the work and results a project is authorized to deliver. Requirements explain what stakeholders need from those results. Managing scope and requirements together helps the team agree on what “done” means, plan the work, and assess proposed changes consistently.
Elicit and define requirements
discovers stakeholder needs and constraints. Useful methods include interviews, workshops, observation, document review, surveys, and prototypes. Involve people who will use, approve, operate, maintain, or be affected by the result, since different groups may have different expectations.
Record each clearly enough to be testable and traceable to a stakeholder need or project objective. A useful record includes an identifier, description, source, priority, rationale, and a way to verify it. For example, “The system shall allow a user to reset a password by email” is more testable than “The system should be user-friendly.”
Review requirements with stakeholders to check that they are necessary, feasible, consistent, and verifiable. and verification are important parts of sound requirements definition.
Define deliverables and boundaries
A is a distinct, reviewable result produced by the project. Examples include an approved design, working product, training materials, or a handover package. State for each major so the team and customer can judge whether it is complete.
Define important as well: work or results that stakeholders might otherwise assume are included. For an online-store launch, the agreed scope might include product listings, checkout, and staff training while excluding ongoing product photography and post-launch marketing. Clear boundaries reduce misunderstandings and help distinguish requested additions from work already agreed.
Break approved scope into work
A hierarchically decomposes the project's total authorized scope into deliverables and manageable work packages. It organizes what must be produced, not the sequence or dates for producing it. Decompose each until the work can be estimated, assigned, and monitored effectively.
Include project-management work as well as product work. Check that the WBS covers the complete agreed scope without adding unapproved work. A WBS dictionary can describe each element, its boundaries, owner, and acceptance conditions.
For a small online-store project, a WBS might be:
The WBS provides a basis for building the schedule, assigning responsibility, estimating cost, and tracking progress.
Control scope changes
The is the approved scope definition and its supporting WBS. Once the baseline is approved, a request is not authorized work merely because it seems small or useful. Use an agreed to evaluate and manage requests:
Log the request: Describe the requested change, its reason, and the stakeholder requesting it.
Analyze impact: Assess effects on requirements, deliverables, , cost, schedule, quality, resources, risks, and related work.
Decide: An authorized sponsor, customer, change board, or other designated decision-maker approves, rejects, or defers the request.
Update and communicate: For an approved change, revise affected baselines and records, including requirements, WBS, schedule, and estimates; tell affected stakeholders.
Verify implementation: Confirm that the approved change was completed and accepted.
For example, adding saved payment methods to an online store may require additional security work and testing. Estimate those impacts before approval, then update the plan if the change is authorized. Assessing a change before implementation helps reveal downstream impacts and keeps current project commitments visible.