Business Analysis 101: Elicitation and Collaboration - Collaborative Games, Gamestorming, Brainstorming, Prioritization

What This Is

Collaborative games are structured, interactive activities (e.g., Gamestorming, Brainstorming, Prioritization games) that help a Business Analyst elicit, analyze, and validate requirements while keeping stakeholders engaged. They are typically used during the Elicitation and Collaboration and Requirements Analysis and Design Definition knowledge areas to surface ideas, surface conflicts, and reach consensus quickly.

Real?world example: While rolling out a new CRM system for a sales organization, the BA runs a “Speed?Storm” brainstorming session with sales reps, marketing, and IT to surface every “must?have” field, then uses a “Dot?Voting” prioritization game to decide which custom objects go into the first release.

Key Terms & Techniques

• Gamestorming – A family of visual, hands?on games (e.g., “Affinity Mapping”, “Crazy?8s”) that turn abstract discussions into concrete artifacts. BABOK KA: Elicitation and Collaboration; Deliverable: Workshop artefacts (post?its, affinity diagrams).
• Brainstorming – A free?form idea?generation technique that encourages quantity over quality; ideas are later grouped and refined. KA: Elicitation and Collaboration; Deliverable: Raw idea list.
• Dot?Voting (Voting Matrix) – Participants place stickers (dots) on options to indicate preference; the option with most dots is the highest priority. KA: Requirements Analysis and Design Definition; Deliverable: Prioritized backlog.
• MoSCoW Prioritization – Classifies requirements as Must, Should, Could, Won’t – a simple way to negotiate scope. KA: Requirements Life Cycle Management; Deliverable: Prioritization matrix.
• Impact?Effort Matrix – Plots ideas on a 2?axis grid (impact vs. effort) to surface quick?wins and long?term bets. KA: Strategy Analysis; Deliverable: Quadrant chart.
• Affinity Diagram (KJ Method) – Groups similar ideas together on a wall; reveals themes and hidden relationships. KA: Elicitation and Collaboration; Deliverable: Clustered post?it board.
• Buy?a?Feature Game – Stakeholders are given a budget (e.g., $100) and “spend” on features they value most; the sum of spend determines priority. KA: Requirements Life Cycle Management; Deliverable: Feature?value chart.
• Lean Coffee – Time?boxed, agenda?free discussion where participants vote on topics; helps surface the most pressing issues first. KA: Elicitation and Collaboration; Deliverable: Meeting minutes with ordered topics.
• Six?Thinking?Hat – Participants adopt different “hats” (facts, emotions, risks, benefits, creativity, process) to explore ideas from multiple angles. KA: Requirements Analysis and Design Definition; Deliverable: Structured discussion notes.
• Story?Mapping – Arranges user stories along a horizontal “backbone” (activities) and vertical “slices” (detail) to visualize end?to?end flow and prioritize releases. KA: Requirements Analysis and Design Definition; Deliverable: Story map board.

Step?by?Step / Process Flow

1. Define the objective & participants – Clarify the problem to solve (e.g., “Identify CRM field requirements”) and invite the right mix of business, technical, and end?user stakeholders.
2. Select the appropriate game – Choose a technique that matches the objective (brainstorming for idea generation, MoSCoW for scope negotiation, dot?voting for quick prioritization).
3. Facilitate the session – Set ground rules, explain the rules of the game, and keep time. Capture all artefacts (post?its, voting results, diagrams) on a shared surface or digital board.
4. Synthesize & document outcomes – Convert raw ideas into requirements statements, use cases, or backlog items; apply the chosen prioritization scheme (MoSCoW, Impact?Effort, etc.).
5. Validate with stakeholders – Review the artefacts in a follow?up meeting; obtain sign?off or consensus on the prioritized list.
6. Baseline & communicate – Record the final prioritized requirements in the Requirements Specification (or Product Backlog) and communicate the baseline to the project team for implementation.

Common Mistakes

• Mistake: Treating the game as a “fun” activity and skipping the formal documentation step.
  Correction: BABOK requires that every elicitation output be captured as a Requirements Elicitation Output (e.g., a prioritized backlog) before moving to analysis.

• Mistake: Inviting too many or the wrong stakeholders, leading to “analysis paralysis.”
  Correction: Follow the Stakeholder Map (KA: Stakeholder Management) to select representatives who have decision?making authority and domain knowledge.

• Mistake: Allowing dominant personalities to dictate the outcome (e.g., one person places all the dots).
  Correction: Enforce equal voting rights (e.g., each participant gets the same number of dots) and use anonymous voting when possible.

• Mistake: Jumping straight to a prioritization matrix without first clustering ideas.
  Correction: Use an Affinity Diagram first to group similar ideas; this reduces duplication and improves the quality of the prioritization input.

• Mistake: Assuming the game creates requirements rather than elicits them.
  Correction: Remember that Elicitation is the activity; the output is a set of requirements that still need analysis, validation, and traceability per BABOK.

Certification Exam Tips

1. Know the input/output relationship – In the ECBA/CCBA/CBAP exam, a question will often ask “What is the primary output of a brainstorming session?” Answer: Raw ideas / candidate requirements (not the final prioritized list).
2. Distinguish knowledge areas – Collaborative games belong to Elicitation and Collaboration; if a question asks which KA the BA should use to “reach consensus on scope,” the correct answer is Requirements Life Cycle Management (because that is where prioritization techniques like MoSCoW are applied).
3. Watch for “who does it?” traps – The BA facilitates the game; the participants generate ideas. If a question says “Who decides the final priority?” the answer is Stakeholders (with BA guidance), not the BA alone.
4. Prioritization technique matching – Remember the classic mapping: MoSCoW-scope negotiation, Dot?Voting-quick consensus, Impact?Effort-strategic selection, Buy?a?Feature-value?driven budgeting.

Quick Check Questions

1. Scenario: After a “Crazy?8s” session, the team has 30 raw ideas. The sponsor wants the top three features for the MVP. Which technique should the BA apply next?
   Answer: Dot?Voting.
   Justification: Dot?Voting lets stakeholders quickly indicate preference, surfacing the highest?ranked ideas for immediate prioritization.

2. Scenario: A stakeholder group cannot agree on whether a requirement is a “Must” or a “Should.” Which prioritization method helps resolve this conflict?
   Answer: MoSCoW Prioritization.
   Justification: MoSCoW forces a conversation about necessity versus desirability, providing a clear negotiation framework.

3. Scenario: The BA needs to group 50 post?it ideas into logical themes before any voting takes place. Which collaborative game is appropriate?
   Answer: Affinity Diagram (KJ Method).
   Justification: Affinity Diagram clusters similar ideas, creating a clean set of themes that can later be prioritized.

Last?Minute Cram Sheet (10 one?liners)

1. Elicitation = activity; Requirements = output.
2. Gamestorming lives in the Elicitation and Collaboration knowledge area.
3. Brainstorming produces a raw ideas list (input to analysis).
4. Affinity Diagram-clusters ideas-creates requirements themes.
5. MoSCoW is a scope?negotiation tool (KA: Requirements Life Cycle Management).
6. Dot?Voting = quick prioritization (output = ranked backlog).
7. Impact?Effort Matrix helps identify quick?wins vs. strategic bets.
8. Buy?a?Feature assigns a budget to features-yields priority ranking.
9. Story?Mapping visualizes end?to?end flow and supports release planning.
10. The BA facilitates the game; stakeholders generate and decide on the content.