IIBA Entry Certificate in Business Analysis ECBA Exam Questions

Answer : A

The experiment elicitation technique involves discovering information under controlled conditions or tests. This approach is valuable when theoretical or observed behavior needs to be validated through actual performance or test conditions, often used in prototyping and usability testing.

Exact Extract from BABOK Guide v3 -- Technique 10.16: Experiment:

''Experiments are used to identify information when it is not available from other sources or when it is desirable to confirm an assumption or hypothesis under controlled conditions.''

Answer : D

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.

Answer : D

The correct answer is D. IIBA's Business Analysis Standard explains that business analysis creates value throughout the organization, across strategic, tactical, and operational levels, and over various timeframes. It also emphasizes continuously assessing and prioritizing work to maximize the value being delivered. Because option D includes both continuous evaluation and alignment with immediate and long-term goals, it is the best match to the IIBA view of value creation.

Option A is incorrect because it focuses too narrowly on short-term needs and compliance. IIBA's framework is broader and includes long-term strategic outcomes in addition to tactical and operational value.

Option B is incomplete. Stakeholder feedback is important in business analysis, but value is not created only by responding to stakeholder preferences. IIBA ties value creation to achieving desired outcomes, making sound decisions, and aligning work across multiple organizational horizons.

Option C is not the best answer because it is too narrow and software-focused. Business analysis is not limited to software delivery, and IIBA defines it much more broadly as enabling change and delivering value across the organization.

Answer : A

Decision making is a type of analytical thinking competency that involves clearly validating assumptions and measuring alternatives to arrive at optimal solutions. It supports the evaluation of trade-offs and selection among multiple options based on data, goals, constraints, and stakeholder input.

Key skills include:

Identifying decision criteria

Analyzing alternatives

Understanding impacts and risks

This competency is critical for business analysts as they often guide stakeholders through structured decision-making processes during requirements prioritization, solution assessment, and risk analysis.

BABOK Reference:

Outlined in the Underlying Competencies section of the BABOK Guide, under ''Analytical Thinking and Problem Solving,'' where decision making is emphasized for its importance in selecting the best course of action.

Answer : A

Stakeholder analysis is a technique used by business analysts to understand the attitudes and influence of various stakeholders. This involves identifying stakeholders, assessing their interests, influence, and the impact they can have on the project. Understanding stakeholders' attitudes and influence helps in managing their expectations, securing their support, and mitigating potential risks associated with stakeholder engagement.

: The BABOK Guide discusses stakeholder analysis as a part of the underlying competencies that a business analyst should develop.It is crucial for the success of any initiative to identify stakeholders, analyze their influence and impact levels, and maintain communication with them even when situations or people change1.Additionally, stakeholder relationship management is listed as one of the core business analyst skills in the BABOK Guide2.

Answer : B

The task Trace Requirements ensures that requirements and designs across different levels (business, stakeholder, solution) are consistently aligned with one another. This alignment supports scope management, impact analysis, verification and validation efforts, and change control.

Requirement tracing also:

Clarifies relationships between business needs and solution features.

Enables efficient scope monitoring and helps avoid scope creep.

Supports linking requirements to their source and derived components.

BABOK Guide v3 -- Section 5.1: Trace Requirements:

''The purpose of Trace Requirements is to ensure that requirements and designs at different levels are aligned to one another and to support change analysis, coverage, and allocation.''

Answer : A

When the focus of specifying and modeling is on how a solution will meet requirements, the output is referred to as a design. According to the BABOK Guide v3, design is the usable representation of a solution. It describes the solution components and how they interact to fulfill business needs. This is distinct from requirements, which describe the 'what' rather than the 'how.'

Requirements = What the solution must do

Design = How the solution will do it

BABOK Reference:

Requirements Analysis and Design Definition knowledge area explains that specifying and modeling can result in either requirements or designs depending on the focus of the activity.