Elicitation and Collaboration

Preparing for, conducting, and confirming elicitation while communicating BA information and managing stakeholder collaboration.

5 minutes 5 Questions

Elicitation and Collaboration are fundamental knowledge areas in the Certified Business Analysis Professional (CBAP) framework, essential for gathering requirements and fostering stakeholder engagement. Elicitation is the systematic process of discovering, uncovering, and extracting information fro…

Concepts covered
Elicitation Technique SelectionSupporting Materials and ResourcesConduct ElicitationWorkshops and Facilitated SessionsSurveys and QuestionnairesBrainstorming and Collaborative GamesPrototyping for ElicitationComparing and Validating Elicitation InformationCommunication Formats and Delivery MethodsResolving Stakeholder ConflictsGaining Stakeholder Agreement and Buy-InPrepare for ElicitationScheduling and Logistics PlanningInterviews as an Elicitation TechniqueObservation and Job ShadowingDocument AnalysisFocus GroupsConfirm Elicitation ResultsCommunicate Business Analysis InformationManage Stakeholder Collaboration
Test mode:
Start practice test

CBAP - Elicitation and Collaboration Example Questions

Test your knowledge of Elicitation and Collaboration

Question 1

A business analyst is new to facilitation and has been asked to run a focus group with seven stakeholders to gather opinions about a proposed workflow change. The analyst wants to ensure participants feel comfortable sharing honest feedback. What should the analyst do at the start of the session to encourage open participation?

Correct Answer: Establish ground rules that promote respectful dialogue and confidentiality among all participants

Establishing ground rules that promote respectful dialogue and confidentiality is the correct approach because it creates a psychologically safe environment where participants feel comfortable sharing honest, candid feedback without fear of judgment or repercussions.

Distributing a detailed agenda with every question can lead to rehearsed or overly filtered responses, reducing spontaneity. Asking participants to share job titles and reporting structures can reinforce hierarchy and power dynamics, which inhibits open sharing, especially among junior staff. Presenting the analyst's own perspective introduces bias and anchors the discussion, discouraging participants from offering differing viewpoints.

The key concept tested is facilitation techniques for creating a safe environment in elicitation sessions.

Question 2

A new business analyst is asked to learn how a team processes daily orders. The analyst sits beside a team member and watches them work for a full day. What is this elicitation technique called?

Correct Answer: Job shadowing, a form of observation where the analyst follows and watches a worker perform their tasks

Job shadowing is a specific form of observation where the business analyst follows and watches a stakeholder perform their regular work activities without interfering, which is exactly what the scenario describes.

Active observation involves the analyst interacting and asking questions during the observation, but the scenario only describes watching, not questioning. Process modeling is an analysis technique for documenting workflows, not an elicitation technique for gathering information by watching. Apprenticing would involve the analyst actually performing or replicating the tasks themselves, whereas the scenario states the analyst only watches.

The key concept tested is the distinction between job shadowing (passive observation) and other elicitation techniques within the BABOK observation category.

Question 3

What is the primary purpose of prototyping as an elicitation technique in business analysis?

Correct Answer: To provide a visual model that stakeholders can review and refine to clarify requirements

Prototyping serves as an elicitation technique by providing stakeholders with a visual or working model of the proposed solution, enabling them to interact with it, provide feedback, and iteratively refine requirements that may be difficult to articulate through conversation alone.

A prototype is not a fully functional production-ready system; it is an approximation used for exploration. It does not replace formal documentation of business rules and process flows, as those require separate analysis artifacts. Prototyping complements other elicitation techniques rather than replacing them entirely, since interviews, workshops, and document analysis are still needed for comprehensive requirements gathering.

Key concept tested: understanding prototyping as an iterative, visual elicitation technique for clarifying and validating stakeholder requirements.

More Elicitation and Collaboration questions
537 questions (total)
Practice 100 questions
One session at a time, always new questions