|
| |
Requirements elicitation is the process of collecting and refining stakeholder requirements. Projects are garbage-in-garbage-out meaning that poor quality requirements typically lead to project issues and failures. The following are common examples of requirements elicitation.
Sessions that encourage stakeholders to contribute ideas in a free and unrestrained fashion. Stimulates creativity as it preserves ambiguity.InterviewsSessions designed to explore the problem space and discover requirements using techniques such as ladder interviews.
QuestionnairesA set of questions for stakeholders such as business units, users or customers.Assumptions & ConstraintsSetting some basic assumptions and constraints that provide a structure for requirements. For example, a building renovation project explicitly states a few things that are out of scope such as replacing load-bearing structures.
Capturing requirements from an end-user perspective. For example, requirements for a new office layout that read "As a manager, I want easy access to small private meeting rooms for one-on-one meetings."Use cases are another format for capturing user expectations.WorkshopsMeetings designed to gather or refine requirements. In many cases, requirements conflict or fail to make much sense when considered as a whole. Workshops may be designed to work out these issues.
It is common practice to prioritize requirements on a regular basis. Projects that regularly ship small sets of working functionality tend to be less risky than projects that implement large blocks of requirements together. Prioritization may be conducted by a project sponsor or project control board.
Stakeholders commonly reject their own requirements once they see them implemented. As such, it is helpful to continually refine requirements by putting working prototypes in front of stakeholders.The ongoing process of collecting, refining, reviewing and prioritizing requirements. An important element of requirements management is managing stakeholder expectations. |
| Type | | | Definition | The process of collecting and refining stakeholder requirements. | | Related Concepts | |
Business Analysis
This is the complete list of articles we have written about business analysis.
If you enjoyed this page, please consider bookmarking Simplicable.
A list of business analysis techniques and deliverables.
The common types and formats of requirements.
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.
A definition of requirements management with examples.
The common types of specification.
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 needs analysis.
TrendingThe most popular articles on Simplicable in the past day.
Recent posts or updates on Simplicable.
Site Map
© 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.
|
