Brainstorming is a group elicitation technique where a problem or topic is presented to the group, and participants are asked to produce as many ideas to solve/address the topic as possible1. The purpose of brainstorming is to generate creative and diverse solutions without any constraints or judgments. Therefore, the following statements are true regarding a brainstorming session during requirements elicitation:
All ideas should be visibly recorded. This helps to keep track of the ideas, avoid repetition, and stimulate further thinking2.
The number of ideas should not be limited. This encourages participants to think outside the box and explore different possibilities2.
All ideas should be shared without any discussion, criticism, or evaluation. This creates a safe and supportive environment where participants can freely express their thoughts without fear of rejection or ridicule2.
The statement that is not true regarding a brainstorming session during requirements elicitation is:
The ideas should be generated with a cost or time estimate. This contradicts the principle of brainstorming, which is to avoid any constraints or assumptions that may limit the creativity and diversity of the ideas2. Cost and time estimates are not relevant at this stage of the elicitation process, as they may bias or discourage participants from suggesting certain ideas. Cost and time estimates can be applied later, after the brainstorming session, when the ideas are prioritized and evaluated3. References:
1: CBAP/CCBA Certified Business Analysis Study Guide, 2nd Edition, by Susan Weese and Terri Wagner, Wiley, 2011, page 140.
2: Top 10 Most Common Requirements Elicitation Techniques, section Brainstorming, page 2.
3: An Overview of Requirements Elicitation, section Brainstorming, page 4.