Brainstorming
Sessions that encourage stakeholders to contribute ideas in a free and unrestrained fashion. Stimulates creativity as it preserves ambiguity.Interviews
Sessions designed to explore the problem space and discover requirements using techniques such as ladder interviews.Questionnaires
A set of questions for stakeholders such as business units, users or customers.Assumptions & Constraints
Setting 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.User Stories
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
Use cases are another format for capturing user expectations.Workshops
Meetings 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.Prioritization
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.Prototypes
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.Requirements Management
The ongoing process of collecting, refining, reviewing and prioritizing requirements. An important element of requirements management is managing stakeholder expectations.| Overview: Requirements Elicitation | ||
Type | ||
Definition | The process of collecting and refining stakeholder requirements. | |
Related Concepts | ||
