IIBA ECBA - Entry Certificate in Business Analysis (ECBA)

The correct answer is C. IIBA explains that business analysis creates value by enabling change and improving outcomes across the organization, and this includes continuous evaluation and alignment of solutions with organizational goals. Monitoring and evaluating outcomes helps determine whether the change is delivering the intended value and where adjustments are needed to improve performance.

Option A is incorrect because documentation may support the organization, but documentation alone is not how business analysis primarily enhances organizational performance. Business analysis is focused on enabling value and better outcomes, not just producing artifacts.

Option B is incorrect because writing technology briefs is not a core description of how business analysis improves performance. It may be a communication activity in some contexts, but it does not represent the main performance-enhancing role of business analysis.

Option D is incorrect because business analysis does not narrow its focus only to implementation. IIBA frames business analysis as spanning strategy, initiative, and delivery contexts, with performance improvement requiring broader and ongoing evaluation.

The techniques used for performing reviews in business analysis include:

Inspection: A formal review technique that involves a detailed examination of work products to identify defects.

Formal Walkthrough: A structured review process where the author leads team members and stakeholders through the work product to gather feedback.

Desk Check: An informal review where the author checks the work product for errors before formal reviews.

These techniques are essential for ensuring the quality and accuracy of business analysis deliverables.

Reference from BABOK® Guide v3:

" Walkthroughs are used for peer reviews and for stakeholder reviews. Single Issue Review (also known as Technical Review): a formal technique focused on either... "

— BABOK® Guide v3, Section 10.37 Reviews

The correct answer is D. BABOK’s requirements classification schema defines business requirements as statements of goals, objectives, and outcomes that describe why a change has been initiated. This is the exact wording used by IIBA, so business requirements are the best and fully correct choice here.

Option A is incorrect because stakeholder requirements describe the needs of stakeholders that must be met to achieve the business requirements. They help bridge the gap between business requirements and more detailed solution requirements, but they do not primarily express why the change was initiated.

Option B is incorrect because solution requirements describe the capabilities and qualities a solution must have in order to meet stakeholder and business needs. They focus on what the solution must do or how well it must perform, not on the original reason for the change.

Option C is incorrect because transition requirements describe temporary capabilities needed to move from the current state to the future state, such as migration, training, or implementation support. They do not state the goals and objectives behind the change.

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.

The BABOK® Guide emphasizes the importance of collaboration when inconsistencies are found between elicitation results. It suggests that business analysts should work together with stakeholders to resolve variations identified in the results. This collaborative approach is essential for ensuring that the information is consistent and accurately represented, and it helps to uncover any discrepancies or ambiguities early in the process, which can prevent costly errors or delays later on.

The information is based on the guidelines provided in the BABOK® Guide, which outlines the best practices for confirming elicitation results and resolving inconsistencies through collaboration123.

A Center of Excellence (CoE) offers standardized practices, tools, techniques, and procedures to enhance the quality and consistency of business analysis efforts across the organization. When a BA uses a CoE, they are typically drawing on pre-established methodologies and best practices to guide their work.

Functions of a CoE:

Maintain organizational BA standards

Provide reusable templates and models

Offer training and professional development

BABOK® Reference:

Covered in the Business Analysis Planning and Monitoring knowledge area, CoEs are identified as a resource for determining appropriate techniques and procedural guidance.

The correct answer is B. Clearly defined and managed business rules help separate policy logic from process flow. This separation makes it easier to update policies, decisions, eligibility conditions, constraints, or calculations without unnecessarily redesigning the entire process. Business rules express operational knowledge and guide or constrain behavior. When they are clearly documented and managed, organizations can adapt to regulatory, strategic, or operational changes more efficiently. Option A reverses the stronger principle; process changes may still require policy review. Option C is incorrect because business rules must still be validated for accuracy and consistency. Option D is incorrect because rules are not merely informal guidelines; many business rules are mandatory constraints that must be followed.

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

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 selecting elicitation techniques, a business analyst should consider techniques that are commonly used in similar initiatives, as these techniques are proven to work in comparable contexts. According to BABOK® Guide v3, the appropriateness of a technique depends on the situation, stakeholders, and the type of information needed. Techniques that have been successful in similar initiatives are likely to produce reliable and familiar results, reduce stakeholder resistance, and improve efficiency.

Exact Extract from BABOK® Guide v3 – Section 4.2: Conduct Elicitation:

“The business analyst considers the characteristics of the source, the type of information to be elicited, the techniques commonly used in similar initiatives, and the time and resource constraints when selecting elicitation techniques.”

When evaluating changes to requirements, in addition to the schedule, it is crucial to consider the number of customers and end-users affected by the change. This factor is important because it directly impacts the value delivery and satisfaction of the stakeholders. The changes must align with the needs and expectations of the customers and end-users to ensure that the solution remains relevant and beneficial. References: This consideration is supported by the Business Analysis Body of Knowledge (BABOK) guide, which emphasizes the importance of stakeholder engagement and value delivery in the requirements management and communication knowledge area1.