Free Practice Questions for IIBA ECBA Exam

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

Business Analysts (BAs) commonly use a checklist during requirements verification to ensure that all requirements are consistent, complete, coherent, and testable. This checklist typically includes a standard set of quality elements that the requirements must adhere to. The use of a checklist helps BAs to systematically verify each requirement against these quality criteria. References: The BABOK Guide lists 8 characteristics of requirements quality: cohesive, complete, consistent, correct, feasible, modifiable, unambiguous, and testable. These characteristics form the basis of the standard quality elements included in a verification checklist1.

The correct answer is A. Business analysis is defined by IIBA as the practice of enabling change in an enterprise by defining needs and recommending solutions that deliver value to stakeholders. Option A is the only answer that preserves the core definition accurately: change, enterprise, needs, solutions, value, and stakeholders. The phrase “while considering context” is also consistent with the Business Analysis Core Concept Model, because business analysis work is always influenced by circumstances such as objectives, constraints, stakeholders, culture, risks, and solution environment. Options B, C, and D are close paraphrases, but they distort the definition by adding terms such as “customer value,” “stakeholder decision-making,” or “stakeholder satisfaction,” which are not the primary formal definition.

===============

In examining relationships between requirements, the criterion of relevance ensures that each requirement is pertinent to the overall goals of the project. This means that all requirements should directly relate to the business needs and objectives, ensuring that they add value and are necessary for the project ' s success. When requirements are relevant, they help in maintaining focus on what is essential, avoiding unnecessary scope creep, and ensuring that resources are used efficiently.

The correct answer is A. IIBA’s Business Analysis Standard and Agile business analysis principles emphasize thinking as a customer and analyzing to determine what is valuable. These ideas align directly with customer focus and value maximization, which are core drivers of effective business analysis work.

Option B is incorrect because although communication and planning matter, this combination does not reflect the central shared values highlighted by IIBA as the primary drivers of business analysis work.

Option C is incorrect because market assessment and management input may be useful in some contexts, but they are not presented by IIBA as the core shared values that broadly drive business analysis.

Option D is incorrect because courtesy and loss minimization are not the recognized IIBA shared values most associated with business analysis practice.

Scope modelling is the technique used to identify the elements and boundaries of the requirements architecture. This technique involves defining what is included within the project or initiative and what is outside its boundaries. Scope modelling helps in clarifying the scope of the work, the features and functions that are to be included in the solution, and any constraints or limitations that should be considered. It provides a structured approach to understanding the overall context and limits of the change being proposed, ensuring that stakeholders have a common understanding of what the initiative aims to achieve and what it does not cover.

According to the BABOK® Guide v3, modeling of requirements can commence with elicitation results in any state. This means that even unconfirmed or preliminary elicitation results can be used to begin modeling, acknowledging that further elicitation may be necessary to refine and validate the models.

Reference from BABOK® Guide v3:

" Elicitation Results (any state): modelling can begin with any elicitation result and may lead to the need for more elicitation to clarify or expand upon requirements. "

— BABOK® Guide v3, Section 7.1.3 Inputs

When a BA considers opportunity costs, they are performing a cost-benefit analysis to determine the best solution. This falls within the task of " Analyze Potential Value and Recommend Solution " , where different design options or requirement implementations are evaluated for their expected value and opportunity costs (what must be forgone when choosing one option over another).

This involves:

Comparing expected benefits vs. associated costs

Evaluating risks and missed opportunities

Recommending the solution with optimal value delivery

BABOK® Reference:

Found in the Requirements Analysis and Design Definition knowledge area, this task emphasizes assessing the relative value of each solution option.

When the number of requirements increases or the level of formality is raised, it becomes more challenging to manage and trace all the requirements. This is because each requirement needs to be documented, analyzed, and tracked throughout the project lifecycle to ensure it is met. As complexity grows, so does the effort required to maintain oversight and ensure that all requirements are accounted for and aligned with the project’s goals.

 User stories are a technique used in business analysis to represent a small, concise statement of functionality or quality needed to deliver value to a specific stakeholder. They are expressed by presenting the role, the goal, or the value and are a fundamental component of Agile methodologies. User stories help teams understand what the stakeholders need without going into excessive detail, allowing for iterative development and refinement of requirements.

The information is verified as per the Business Analysis Learning documents and resources, which discuss various techniques including user stories as a way to capture stakeholder needs and prioritize development of solutions12.