Is the requirement gathering method in projects called when a group tries to find a solution for a specific problem by gathering a list of ideas spontaneously contributed by its members?
No. that's called brainstorming.
Requirement gathering is when the process of deciding which functionality and features will be included in the product and in which platform it will run.
To do that you need to ask Marketing what the users want, the Engineers for what is possible to build Product Management for what is the minimum/maximum effect you're aiming to produce, and in what budget.
These are the steps of gathering requirements:
- Ask Questions to domain experts
- Analyze and observe the old process and opportunities to add features
- Create prototype
- Brainstorming is a must... if you put quality time on it, then you will ask questions and in return you will have answers. Make an activity or flow diagram based on what you have gathered... most important is "Listen, note and verify"
- Do workshops in department functional body
These sections of the PMBOK (Project Management Book of Knowledge) form the basis of what you're looking for.
Part 1, Chapter 5 (Project Scope Management)
- Section 5.2 (Collect Requirements) and its three subsections;
- 5.2.1 (Collect Requirements: Inputs)
- 5.2.2 (Collect Requirements: Tools and Techniques
- 5.2.3 (Collect Requirements: Outputs)
Collect Requirements is the process of determining, documenting and managing stakeholder needs and requirements to meet objectives. The key benefit of this process is that it provides the basis for defining the product scope and project scope. This process is performed once or at predefined points in the project.
Here's a chart of the inputs, tools & techniques, and outputs of this process. (As you can see, Brainstorming is a type of Data Gathering under the Tools & Techniques section.)
Here's a data flow diagram of the process.
Part 2, Chapter 3 (Planning Process Group)
- Section 3.3 (Collect Requirements) and its two subsections
- 3.3.1 (Project Management Plan Components)
- 3.3.2 (Project Documents Examples)
Examples of project management plan components that may be inputs for this process include, but are not limited to:
- Scope management plan,
- Requirements management plan, and
- Stakeholder engagement plan.
Examples of project documents that may be inputs for this process include but are not limited to:
- Assumption log,
- Lessons learned register, and
- Stakeholder register.