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.
Explanation
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.
Test your knowledge
Practice scenario-based questions on this topic with detailed explanations.