Certification of Capability in Business Analysis (CCBA) — Lesson 2: Elicitation, Collaboration, Evidence Review, and Problem Investigation

Learning Objectives

• Identify the dependencies connecting elicitation objectives, collaboration methods, and evidence quality across the workflow.
• Validate a elicitation evidence log and problem analysis against explicit acceptance evidence.
• Explain which cause is sufficiently supported to guide requirement and design work after testing the stated exception.

Detailed Topics

• Clarify elicitation objectives by identifying purpose, ownership, boundaries, dependencies, and decision criteria.
• Apply collaboration methods to the scenario and preserve the evidence supporting the selected approach.
• Compare alternatives for evidence quality and explain practical value, risk, and operating consequences.
• Challenge root-cause analysis with a realistic exception that exposes assumptions or weak accountability.
• Document knowledge confirmation with acceptance conditions, review responsibility, and a clear next action.

Instructor Demonstration

The instructor demonstrates how to investigate an operational issue using interviews, workshops, records, and direct observation. The walkthrough explains which cause is sufficiently supported to guide requirement and design work, builds the elicitation evidence log and problem analysis, and tests the exception where a visible symptom is treated as the root cause without testing process and information evidence.

Hands-On Exercise

Complete a controlled exercise to investigate an operational issue using interviews, workshops, records, and direct observation and preserve the result in the elicitation evidence log and problem analysis.

1. Confirm the facts, stakeholders, constraints, evidence sources, and success conditions relevant to elicitation objectives.
2. Perform the central analysis involving collaboration methods, evidence quality, and root-cause analysis.
3. Introduce the exception where a visible symptom is treated as the root cause without testing process and information evidence and revise the proposed response.
4. Complete the elicitation evidence log and problem analysis with ownership, acceptance evidence, unresolved concerns, and follow-up actions.

Scenario Analysis

• Identify the assumption with the greatest influence on which cause is sufficiently supported to guide requirement and design work.
• Compare two defensible responses involving root-cause analysis and explain their trade-offs.
• Specify the evidence required before the elicitation evidence log and problem analysis can be accepted.

Troubleshooting Guidance

Trace the first difference between the intended outcome and the available evidence. Recheck scope, roles, source quality, dependencies, decision criteria, and retained records independently. The analysis remains incomplete while a visible symptom is treated as the root cause without testing process and information evidence.

Validation Checklist

• Scope and ownership for elicitation objectives are explicit.
• The selected treatment for collaboration methods is supported by reviewable evidence.
• The exception involving root-cause analysis was tested and its impact recorded.
• The elicitation evidence log and problem analysis contains acceptance criteria, accountable owners, and next actions.

Lesson Outcome

Learners can apply Elicitation, Collaboration, Evidence Review, and Problem Investigation, explain which cause is sufficiently supported to guide requirement and design work, and support the conclusion with a elicitation evidence log and problem analysis.