Which process involves gathering stakeholder needs for a project?

The process that involves gathering stakeholder needs for a project is termed "Collect Requirements." This phase is critical because it focuses on identifying, analyzing, and documenting the needs and expectations of project stakeholders. By actively engaging stakeholders during this process, project managers can ensure that the requirements reflect the true needs and desires of those impacted by the project, leading to greater satisfaction and project success.

In this stage, various techniques may be employed, such as interviews, surveys, focus groups, and workshops, to elicit comprehensive information from stakeholders. The result is a clear and detailed set of requirements that can be used as the foundation for subsequent project planning and execution.

While defining scope, controlling scope, and creating a Work Breakdown Structure (WBS) are all important components of project management, they occur after the requirements have been collected. Defining scope clarifies what work will be included in the project based on the requirements gathered. Control scope involves monitoring and managing changes to the project scope over time. Creating a WBS organizes the project scope into manageable sections but relies on the requirements identified during the Collect Requirements phase. Therefore, "Collect Requirements" is the correct process that directly relates to gathering stakeholder needs.