product requirements document, PRD, user requirements capture, user requirements, collecting requirements, user needs research
Requirements gathering is the process of generating a list of requirements from the various stakeholders or customers, users that will be used as the basis. These practices include interviews, questionnaires, user observation, workshops, brainstorming, use cases, role playing and prototyping.
Meme
There is famous cartoon entitled “Project Cartoon” captures the sad reality behind bad requirements gathering:
Controversial
«gather dust»
The requirements gathering process may appear simple, but often may arise issues that complicate it. Most challenges were indicated in 1992 by Christel and Kang:
Problems of scope
The boundary is ill-defined
Users specify unnecessary details
Problems of understanding
Poor understanding of the capabilities and limitations
Problems of volatility
Undocumented processes
Conflicting requirements
Lack of access to end users
Focusing on visual aspects rather than on functional
Adequate, timely and effective consultation of relevant stakeholders is of paramount importance in the requirements engineering process. However, the thorny issue of making sure that all relevant stakeholders are consulted has received less attention than other areas which depend on it, such as scenario-based requirements, involving users in development, negotiating between different viewpoints and so on
FAQs
Share the term
Design with FlowMapp Tools
Try free our Tools for successful management and development of web projects
Requirements gathering is the process of generating a list of requirements from the various stakeholders or customers, users that will be used as the basis
Read more
.svg)
.svg)
.svg)
.svg)
