Chapter 3: Project Scope, Requirements and Stakeholder Management
Undergraduate Bachelor of Project Management · Year 1 · Full study notes, applied methods and assessment guide
Chapter overview
This chapter develops undergraduate-level understanding of project scope, requirements and stakeholder management. It combines conceptual explanations, practical methods, decision frameworks, worked examples and applied cases. Students should connect each method to project context, governance, people, evidence and measurable outcomes rather than treating tools as isolated templates.
Learning outcomes: explain the chapter's key terminology; apply relevant methods to a realistic project; interpret evidence and assumptions; evaluate limitations and risks; communicate a defensible recommendation; and connect project outputs with stakeholder needs and intended benefits.
Concept map: Project Scope, Requirements and Stakeholder Management
This diagram is a learning aid. Apply the sequence to the chapter topics and identify the feedback loops needed when assumptions or conditions change.
Project scope defines the work required to produce the agreed deliverables and the boundaries of what is excluded. Product scope describes the characteristics and functions of the result; project scope describes the work needed to create it. Confusing the two creates disputes. A requirement for a secure digital service is a product characteristic; analysing needs, designing, configuring, testing, training and transitioning the service are project work. Scope management establishes how requirements are collected, defined, validated and controlled. It provides a basis for estimating, scheduling, procurement and acceptance.
In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.
A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.
2. Requirements elicitation
Requirements are gathered through interviews, workshops, observation, surveys, document analysis, process mapping, prototypes, data analysis and review of regulations or standards. Select methods based on the type of information needed. Interviews can reveal individual concerns; workshops expose conflicts and build shared understanding; observation reveals workarounds that people may not mention; prototypes help users respond to something tangible. Include representative users, including people with accessibility needs or limited digital access. Record the source, rationale, priority and validation status of each important requirement.
In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.
A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.
3. Functional and non-functional requirements
Functional requirements describe what a product or service must do, such as register a user, calculate a fee or issue an alert. Non-functional requirements describe qualities and constraints such as security, reliability, performance, usability, accessibility, maintainability, privacy and compatibility. Both are essential. A platform may perform every requested function but still fail if it is too slow, inaccessible or insecure. Non-functional requirements should be measurable where possible. For example, replace 'fast response' with an agreed response-time threshold under a stated user load and test condition.
In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.
A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.
4. Requirements quality and prioritisation
Good requirements are clear, necessary, feasible, testable, traceable, consistent and unambiguous. Avoid compound statements that combine several conditions. Prioritisation methods include MoSCoW (must, should, could, will not for now), weighted scoring, value-versus-effort analysis and risk-based ranking. Priorities should be agreed with authorised stakeholders. A must-have requirement should have a reason, such as legal compliance, safety or essential service capability. If every request is labelled mandatory, prioritisation has failed and the team cannot make rational trade-offs when time or funding is constrained.
In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.
A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.
5. Requirements traceability
A requirements traceability matrix links each requirement to its source, design response, work package, test, acceptance evidence and owner. Traceability helps show that the project has addressed the need and prevents unrequested features from entering unnoticed. It also supports impact analysis when a requirement changes. A traceability matrix should be maintained as a live control, not created once for an audit. For complex projects, use a requirements management system with version control and relationships between parent and child requirements.
In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.
A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.
6. Project scope statement
The scope statement describes objectives, deliverables, boundaries, assumptions, constraints, acceptance criteria and exclusions. It should be detailed enough to guide planning but not pretend that every detail is known before investigation. Assumptions should be explicit because an incorrect assumption can create major cost or schedule effects. Exclusions are especially useful: state what the project will not provide, who will own related work and how interfaces will be managed. A scope statement should be approved by the people authorised to commit resources and accept the deliverables.
In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.
A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.
7. Work breakdown structure
A work breakdown structure (WBS) decomposes the total project scope into manageable components. It is deliverable-oriented: it organises what must be produced rather than merely listing chronological activities. The 100% rule means the WBS should include all authorised project work and only that work. Lower levels provide greater detail. A work package is a manageable unit that can be estimated, assigned, scheduled and controlled. WBS coding provides a consistent reference for cost accounts, schedule activities, risk records and progress reports.
In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.
A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.
8. WBS dictionary and scope baseline
The WBS dictionary explains each component, including description, boundaries, deliverables, assumptions, responsible owner, acceptance criteria and interfaces. Together, the approved scope statement, WBS and WBS dictionary form the scope baseline in many project control systems. A baseline is not an unchangeable document; it is the authorised reference against which performance and proposed changes are assessed. Changes should follow the agreed control process, with updated versions and a record of approvals.
In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.
A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.
9. Scope verification and acceptance
Scope verification is the process of reviewing completed deliverables with the authorised customer, sponsor or user representative to confirm that they meet documented acceptance criteria. Verification asks whether the deliverable conforms to requirements; validation asks whether it meets the real need in its intended context. A system can pass functional tests yet fail user acceptance because the workflow does not fit actual practice. Acceptance evidence may include inspection, test results, certificates, demonstrations, signed checklists or formal approval. Defects and outstanding items should be recorded and resolved under agreed rules.
In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.
A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.
10. Stakeholder identification
Stakeholder identification should begin early and continue throughout the project. Start with the sponsor, client, users, delivery team, suppliers, regulators, funders and operational owners, then consider indirect and potentially affected groups. Stakeholders may be internal or external, supportive or resistant, highly influential or directly impacted. Record why each stakeholder matters, their interests, decision authority, likely concerns and preferred engagement methods. Do not assume that one representative speaks for an entire community or user group.
In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.
A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.
11. Stakeholder analysis
Power-interest grids can help tailor engagement, but they should be used carefully. High-power, high-interest stakeholders often need close involvement; high-power, low-interest stakeholders need concise assurance; low-power, high-impact groups still require meaningful engagement because their lives may be affected. Salience analysis considers power, legitimacy and urgency. Impact analysis asks who experiences changes and whether benefits or burdens are distributed fairly. Stakeholder analysis is a working hypothesis: update it when roles, influence, concerns or project conditions change.
In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.
A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.
12. Communication and engagement planning
Communication planning defines what information is needed, by whom, when, in what format, from which owner and through which channel. Engagement is broader than sending information: it involves listening, dialogue, participation and response. A regulator may need formal submissions; a site team may need daily coordination; community members may prefer accessible meetings and clear notices; senior sponsors may need concise exception reports. Communication should be timely, accurate, inclusive and proportionate. Translation, accessible formats, data protection and confidentiality should be considered.
In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.
A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.
13. Conflict and negotiation
Stakeholder conflict can arise from competing priorities, scarce resources, different risk perceptions, unclear requirements or unequal power. Avoid treating all disagreement as obstruction. Structured negotiation identifies interests beneath stated positions, develops options, tests objective criteria and records agreements. A stakeholder demanding a larger facility may actually need capacity at peak times; a different operating model might meet the need at lower cost. Where agreement is impossible, escalate the decision to the authorised governance body with transparent options and consequences.
In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.
A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.
14. Change requests and scope control
A change request describes the proposed alteration, reason, urgency, originator and expected benefit. Impact analysis considers scope, schedule, cost, quality, resources, risks, contracts, operations, accessibility and benefits. The change authority approves, rejects, defers or requests more evidence within delegated limits. Approved changes are incorporated into baselines and communicated to affected parties. Unapproved work should not quietly enter delivery because it creates scope creep and weakens accountability. Emergency changes need a defined route and retrospective record.
In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.
A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.
15. Acceptance criteria and definition of done
Acceptance criteria state the conditions a deliverable must satisfy before it is accepted. They should be agreed before completion and written so that evidence can be checked. A definition of done may include completed functionality, passed tests, documentation, security review, user training, accessibility checks and handover readiness. Acceptance should not be confused with payment certification unless the contract explicitly links them. In staged delivery, each increment may have its own criteria while the overall solution has system-level acceptance conditions.
In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.
A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.
16. Scope and stakeholder interfaces
Many scope disputes occur at interfaces: one supplier assumes another will provide power, a client expects training but the contract excludes it, or a design team assumes a regulator will approve a solution without a formal submission. Interface registers identify boundaries, inputs, outputs, owners, timing and acceptance. Interface workshops help resolve gaps before they become claims or delays. Requirements should be allocated to the correct work package and contract, with dependencies visible in the schedule.
In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.
A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.
17. Case study: community water project
A community water project must define who will receive service, expected capacity, water-quality requirements, collection points, operating hours, maintenance arrangements and environmental safeguards. Stakeholders include households, local leaders, landowners, water authorities, contractors, health officers and future operators. Requirements elicitation should include women, people with disabilities and remote households who may experience different access barriers. The WBS could include survey, design, permits, source development, treatment, storage, distribution, testing and operator training. Acceptance criteria should include verified water quality, safe construction records, functioning assets and a funded maintenance plan.
In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.
A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.
18. Common scope and engagement errors
Common errors include writing a solution before understanding the problem, collecting requirements only from senior managers, omitting non-functional needs, using vague acceptance criteria, failing to record exclusions, allowing informal changes and treating consultation as a one-way announcement. Another error is over-documenting low-risk work while neglecting critical interfaces. The remedy is proportional rigour: define what matters, involve the right people, maintain traceability, test deliverables against agreed criteria and make decisions visible.
In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.
A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.
Additional applied study: Requirements validation and prioritisation workshop
A validation workshop brings users, sponsor representatives, technical specialists and operational owners together to review whether requirements are complete, understandable, feasible and aligned with the intended outcomes. Participants should examine conflicts, duplicates, assumptions and missing user groups. Priorities can be agreed using value, urgency, compliance, risk and implementation effort. Record decisions and unresolved questions with named owners and due dates. A workshop should not force consensus where evidence is incomplete; it should make disagreement visible and establish the next investigation. Follow-up validation with people who could not attend helps reduce the risk that a small group defines the needs of a wider population.
For assessment, support your analysis with a clear project example, state the assumptions used and explain how the team would record, communicate and review the decision. Strong answers distinguish a method's intended benefit from its limitations and show how it connects to the approved project objectives.
Requirements may change because users learn from prototypes, regulations change, technology constraints emerge or the operating environment shifts. Volatility is not always a failure; unmanaged volatility is. Establish a change threshold, version control, impact analysis and a decision authority. Group related changes and examine cumulative effects because many individually small requests can materially increase cost and complexity. For iterative delivery, maintain a prioritised backlog and agree how items enter a release. For predictive delivery, baseline requirements and route proposed changes through formal control. In both cases, retain traceability from the original need to the delivered and accepted capability.
For assessment, support your analysis with a clear project example, state the assumptions used and explain how the team would record, communicate and review the decision. Strong answers distinguish a method's intended benefit from its limitations and show how it connects to the approved project objectives.
Engagement should be evaluated by the quality of participation and the influence it has on decisions, not by counting meetings alone. Useful measures include stakeholder understanding, response time to concerns, representation of affected groups, closure of feedback actions, unresolved objections and user acceptance. Document what was heard, what changed and why some suggestions were not adopted. Protect personal information and avoid publishing sensitive comments without permission. If a stakeholder group remains disengaged, investigate whether the channel, timing, language, accessibility or power imbalance is preventing participation. Review engagement plans throughout delivery.
For assessment, support your analysis with a clear project example, state the assumptions used and explain how the team would record, communicate and review the decision. Strong answers distinguish a method's intended benefit from its limitations and show how it connects to the approved project objectives.
University examination and revision questions
Attempt each question using definitions, explanation, evidence, examples and evaluation. Where a question asks for application, state your assumptions and show how the method would be used in a real project.
Question 1: Define the central concept in this chapter and explain why it matters.
Model answer: A strong answer defines the concept precisely, identifies its purpose, explains its relationship with other project controls and gives a practical example. It should distinguish the concept from related terms and state the consequences of applying it poorly.
Question 2: Explain how the chapter's methods support project decision-making.
Model answer: The methods organise evidence, clarify assumptions, expose dependencies and make trade-offs visible. They support decisions when their inputs are reliable, their limitations are understood and the decision is made by an authorised person.
Question 3: Discuss three common implementation challenges and suitable responses.
Model answer: Typical challenges include incomplete information, competing stakeholder priorities and limited resources. Responses include early engagement, transparent prioritisation, realistic estimates, explicit ownership, risk review and controlled change.
Question 4: Apply the chapter to a public-sector or organisational project.
Model answer: Begin with the need and intended beneficiaries. Define the deliverables, constraints and stakeholders; select relevant tools; identify risks and controls; explain how progress will be measured; and state how the output will be accepted and sustained.
Question 5: Evaluate why professional judgement remains necessary when using project tools.
Model answer: Tools simplify complex conditions and depend on assumptions. Professional judgement is required to interpret evidence, identify bias, assess context, understand ethical consequences and decide when specialist advice or escalation is necessary.
Chapter summary
This chapter develops undergraduate-level understanding of project scope, requirements and stakeholder management. It combines conceptual explanations, practical methods, decision frameworks, worked examples and applied cases. Students should connect each method to project context, governance, people, evidence and measurable outcomes rather than treating tools as isolated templates. The central lesson is to use project management methods as connected decision aids. Maintain clear ownership, test assumptions, communicate honestly, involve affected stakeholders and review evidence as the project evolves. A sound method is only valuable when it improves decisions and contributes to a result that can be accepted, operated and sustained.
Official Education References
Use these official organisations for curriculum guidance, examinations and further learning information.