Which process is primarily used to identify and document stakeholder needs and requirements?

Prepare for the PMI GMetrix Test with comprehensive quizzes. Utilize flashcards, practice multiple choice questions, and study detailed explanations to excel in your exam. Elevate your confidence and get exam ready today!

Multiple Choice

Which process is primarily used to identify and document stakeholder needs and requirements?

Explanation:
Collecting requirements is the process used to determine, document, and manage stakeholder needs and requirements for a project. It involves engaging with stakeholders through interviews, workshops, focus groups, surveys, observation, and prototyping to uncover both functional needs (what the project should do) and nonfunctional needs (quality attributes, constraints). The goal is to produce a clear, validated set of requirements that guides scope definition and the overall solution design. Key outputs include Requirements Documentation and the Requirements Traceability Matrix, which links each requirement back to higher-level objectives and forward to design, development, and testing. This focus on gathering and recording what stakeholders expect distinguishes it from other planning activities, such as planning communications (how information will be shared), planning resources (what people and materials are needed), or defining the scope (describing the project’s deliverables in detail).

Collecting requirements is the process used to determine, document, and manage stakeholder needs and requirements for a project. It involves engaging with stakeholders through interviews, workshops, focus groups, surveys, observation, and prototyping to uncover both functional needs (what the project should do) and nonfunctional needs (quality attributes, constraints). The goal is to produce a clear, validated set of requirements that guides scope definition and the overall solution design. Key outputs include Requirements Documentation and the Requirements Traceability Matrix, which links each requirement back to higher-level objectives and forward to design, development, and testing.

This focus on gathering and recording what stakeholders expect distinguishes it from other planning activities, such as planning communications (how information will be shared), planning resources (what people and materials are needed), or defining the scope (describing the project’s deliverables in detail).

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy