Stakeholder Requirements
Stakeholder requirements describe the needs of individual stakeholders or stakeholder groups, including what they need the solution to do for them in order to meet the business requirements.
Know it well enough for the exam? Questions on Stakeholder Requirements are scenario-based, not definitional.
Practice it freeExplanation
Stakeholder requirements bridge the gap between high-level business requirements and detailed solution requirements. They capture the specific needs, expectations, and desires of the people who will use, be affected by, or have authority over the project's outcome. Each stakeholder group may have different and sometimes conflicting requirements.
For example, end users might require an intuitive interface, managers might require detailed reporting capabilities, and compliance officers might require audit trails. The business analyst gathers these through elicitation techniques like interviews, focus groups, and surveys, then analyzes and documents them to ensure completeness and consistency.
Stakeholder requirements must be traceable upward to business requirements and downward to solution requirements. When conflicts arise between stakeholder groups, the business analyst facilitates prioritization and negotiation to reach consensus, always keeping business requirements as the guiding principle. Unmanaged stakeholder requirements are a leading cause of project scope creep and stakeholder dissatisfaction.
Key Points
- •Describe what individual stakeholders or groups need from the solution
- •Bridge business requirements and solution requirements in the requirements hierarchy
- •Gathered through elicitation techniques like interviews, focus groups, and surveys
- •Must be prioritized and reconciled when conflicts arise between stakeholder groups
Exam Tip
Know where stakeholder requirements sit in the hierarchy: below business requirements and above solution requirements. Conflicts must be resolved through prioritization.
Frequently Asked Questions
Related Topics
Business Requirements
Business requirements describe the high-level needs of the organization, including why the project is being undertaken, the business goals it supports, and the measurable objectives it must achieve.
Solution Requirements
Solution requirements describe the characteristics, features, and capabilities that a solution must possess to meet business and stakeholder requirements. They are divided into functional and non-functional requirements.
Requirements Prioritization
Requirements prioritization is the process of ranking requirements by importance, urgency, risk, and business value to determine the order in which they should be addressed given constraints on time, budget, and resources.
Elicitation Techniques (Business Analysis)
Elicitation techniques are structured methods used by business analysts to gather requirements and information from stakeholders, including interviews, workshops, observation, surveys, document analysis, prototyping, and brainstorming.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Burndown Chart
A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.
Burn-Up Chart
A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.
Resource Leveling
Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.
Deliverables
A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.
Power Interest Grid (Power/Influence Grid)
The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.
Critical Path Method (CPM)
The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.
Weighted Shortest Job First (WSJF)
Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.
Risk Register
The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.
Stakeholder Mapping
Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.
Part of
CAPM-Specific Concepts
Practice Stakeholder Requirements
Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.