Stakeholder requirements are requirements that are collected from stakeholders such as business units, operations teams, customers, users, communities and subject matter experts. The following are illustrative examples of stakeholder requirements.
Business units may provide user stories or detailed requirements depending on their role in the project. Generally speaking, business units have the last word on functionality, features and quality requirements.
Operational requirements such as maintenance features of software. Operations teams may also contribute constraints such as those related to the capabilities of a production line. Customers such as a lead user may contribute user stories or ideas for usability and quality. For example, "As a customer with kids, I'd like basic control buttons on the back of the television for the times when I lose the remote."
UsersUsers may be asked to contribute ideas for functionality, features, usability and quality. Users of business software and processes may be primarily interested in productivity features. For example, "As an Order Manager, I'd like to see all active orders in a single screen, because I need to see that dozens of times a day."
Requirements from subject matter experts in areas such as architecture, engineering, design, usability, technology, construction, legal and compliance. For example, an information security consultant who contributes non-functional requirements to a bank's infrastructure project.
This is the complete list of articles we have written about business analysis.
If you enjoyed this page, please consider bookmarking Simplicable.
The common types and formats of requirements.
The difference between functional and non-functional requirements explained.
The difference between requirements and specifications.
The difference between functional and behavioral requirements explained.
A few examples of non-functional requirements.
A definition of requirements traceability with examples.
The common types of customer requirements.
The difference between functions and features.
The common types of requirements elicitation.
A definition of requirements management with examples.
The common types of needs analysis.
A list of business analysis techniques and deliverables.
The difference between business analysis and business architecture.
A few examples of common process gaps.
A definition of best in class with examples.
The common types of data analysis.
Common types of technical feasibility.
The common types of specification.
TrendingThe most popular articles on Simplicable in the past day.
Recent posts or updates on Simplicable.
© 2010-2023 Simplicable. All Rights Reserved. Reproduction of materials found on this site, in any form, without explicit permission is prohibited.
View credits & copyrights or citation information for this page.