1

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?

3

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.

  • 1
    Please provide evidence for your claims that the following aspects are part of "Requirements Gathering": 1) The decision which functionality and features actually will make it into the product and 2) that requirements must specify "on which platform a product will run". Furthermore: 3) Have you heard of non-functional requirements? In other words, in my view your definition of "Requirements Gathering" (if at all) only applies to simple small-scale software products. Finally, the Q is about "Requirements Gathering Methods", where brainstorming actually may play a certain role. – loom with a crew Dec 28 '18 at 11:14
2

These are the steps of gathering requirements:

enter image description here

  1. Ask Questions to domain experts
  2. Analyze and observe the old process and opportunities to add features
  3. Create prototype
  4. 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"
  5. Do workshops in department functional body
2

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.)

enter image description here

Here's a data flow diagram of the process.

enter image description here


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)

Here are the input and outputs of this process: enter image description here

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.
  • 2
    Consider adding more information so that we don't need to go to the book to get the answer for the question. – Tiago supports GoFundMonica Aug 28 at 23:09
  • 1
    I've added more information, but as this process comprises a considerable amount of information I gave what I felt was most relevant in my edit... – richardlpalmer Aug 29 at 14:51
  • 1
    Much better @richardlpalmer ;) – Tiago supports GoFundMonica Aug 29 at 17:18

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.