IIBA ECBA Dumps - Pass Entry Certificate in Business Analysis Exam in First Attempt 2026

The correct answer is B. IIBA's Business Analysis Standard states that an adaptive or iterative approach focuses on delivering value in small, prioritized increments. This is the clearest direct match to option B.

Option A is more characteristic of a predictive approach, where planning is done more extensively upfront and execution follows the established plan.

Option C is incorrect because adaptive approaches do not focus primarily on descriptive documents; they emphasize incremental value delivery and just-enough, just-in-time documentation.

Option D is also more aligned with predictive thinking, where progress is measured against a plan established in advance. Adaptive approaches continuously refine the work based on learning and priorities.

When a stakeholder seeks to understand the logistics and scope of each elicitation activity, the Business Analyst should share the elicitation activity plan. This plan outlines the objectives, techniques, stakeholders involved, and the schedule for each elicitation activity, providing clarity and setting expectations.

Reference from BABOK Guide v3:

'Prepare for Elicitation: describes the tasks that the business analyst performs to prepare for elicitation activities. It includes determining the types of activities, the techniques, and the logistics required.'

--- BABOK Guide v3, Section 4.1

Traceability is a tool used in business analysis to track the life of a requirement from its origin through its development and specification, to its subsequent deployment and use, and through periods of ongoing refinement and iteration in any of these phases. It allows business analysts to determine the impact of changes in requirements by providing a clear path of how each requirement is connected to others, which is essential for assessing the consequences of changes.

: The BABOK Guide emphasizes the importance of traceability in managing and analyzing the impact of changes in requirements. It is a fundamental aspect of requirements management and communication, one of the six knowledge areas defined in the BABOK Guide.Traceability supports several tasks within this knowledge area, including maintaining requirements for reuse, preparing requirements for change, and evaluating the potential impact of changes1.

In the context of Business Analysis, elicitation through experiments involves conducting controlled tests to obtain information. This method is used to identify results based on tests run in a controlled environment, which can include proof of concepts, observational studies, and prototypes. It is a systematic approach to discovering requirements by validating hypotheses through experimentation.

: The information aligns with the descriptions provided in the Business Analysis Body of Knowledge (BABOK) and is further supported by resources that discuss various elicitation techniques, including experiments as a form of elicitation1.

User stories are a fundamental component in Agile methodologies, serving as concise, user-centric descriptions of desired functionalities. They are designed to facilitate communication among stakeholders and ensure that the development team understands the requirements from the user's perspective.

Key Elements of User Stories:

Title: A brief, descriptive name that captures the essence of the user story. It helps in identifying and referencing the story easily.

Statement of Value: This follows the format: 'As a [user role], I want [goal] so that [benefit].' It clearly articulates who the user is, what they need, and why they need it, ensuring that the focus remains on delivering value.

Conversation: Represents the collaborative discussions between stakeholders and the development team. These conversations delve deeper into the details of the user story, clarifying requirements and expectations.

Acceptance Criteria: Specific conditions that must be met for the user story to be considered complete. They provide a clear definition of done and guide the development and testing processes.

Reference from BABOK Guide v3:

According to the BABOK Guide v3, user stories are a technique used to capture a description of a software feature from an end-user perspective. They are typically composed of a title, a statement of value, conversations to elaborate on the details, and acceptance criteria to define the boundaries and conditions for success.