Pass the IIBA Entry Certificate in Business Analysis ECBA Questions and answers with ExamsMirror

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.”

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 correct answer is A . In BABOK, Maintain Requirements includes maintaining requirements for reuse , and IIBA explicitly notes that reuse helps extend value beyond the current initiative . Planning for reuse avoids recreating the same requirements repeatedly, which improves efficiency and reduces duplicated effort.

Option B is not the best answer because aligning requirements to organizational standards may be beneficial, but that is not the main BABOK reason for planning reuse. The stronger ECBA-aligned reason is improving efficiency and reducing repeated work across initiatives.

Option C is incorrect because collaboration and communication may improve indirectly, but BABOK does not present reuse primarily as a collaboration mechanism.

Option D is incorrect because reuse is intended to simplify and streamline analysis work, not increase complexity.

Personal accountability is a critical behavioral characteristic for business analysis professionals. It ensures that the tasks performed meet stakeholder expectations by holding the professional responsible for their actions and decisions. Personal accountability drives a commitment to delivering quality work, adhering to timelines, and maintaining transparency in communication. This characteristic fosters trust and reliability, ensuring that stakeholders can depend on the business analyst to meet their needs and expectations effectively.

In the context of business analysis, interviews are a fundamental elicitation technique used to gather detailed information. There are two basic types of interviews: structured and unstructured. A structured interview is one where the interviewer comes prepared with a specific set of questions that are asked in a systematic manner. This approach ensures consistency and comparability of responses. On the other hand, an unstructured interview is more flexible, allowing the conversation to flow more naturally based on the interviewee’s responses.  This can lead to the discovery of information that might not have been uncovered through a structured approach.  References : The information aligns with the guidelines provided by the International Institute of Business Analysis (IIBA) and is verified according to their standards for elicitation techniques 1 2 .

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.

 Stakeholder requirements describe the needs of those participating in or impacted by business analysis activities. These requirements focus on ensuring that the perspectives and needs of all stakeholders are considered and integrated into the solution.  Stakeholder requirements are essential for understanding the context of the business needs and for defining the criteria for the success of the solution.  References : The information is verified as per the Business Analysis Learning documents, specifically the BABOK Guide, which outlines the types of requirements including Business, Stakeholder, Solution, and Transition Requirements 1 .

Document analysis is a technique used in business analysis for eliciting information by reviewing existing documentation. This can include analyzing current business documents, user manuals, and any other material that provides insight into the business environment or existing organizational assets. It helps in understanding the current state of affairs, identifying requirements, and uncovering areas for improvement.

The correct answer is C . BABOK describes Lessons Learned as a technique used to identify changes to business analysis processes and deliverables, as well as successes that can be incorporated into future work . The purpose is to use experience from what happened before to improve current practice and influence future initiatives.

Option A is incorrect because getting consultant feedback may happen in some situations, but it is not the purpose of the lessons learned technique in BABOK. The focus is organizational learning and improvement.

Option B is incorrect because lessons learned are not meant to be kept confidential within only the BA team. Their value comes from sharing relevant insights so processes and outcomes can improve more broadly.

Option D is incorrect because lessons learned are meant to support improvement, not delay documentation unnecessarily. In many environments, especially iterative ones, learning is captured and applied continuously rather than postponed until the very end.

A solution is considered successful when it satisfies the business need it was intended to address. This means that the solution has effectively resolved the problem or fulfilled the requirement that prompted its development. While meeting stakeholders’ expectations, ensuring the organization is ready to accept the solution, and having a positive performance evaluation are all important, they are secondary to the primary goal of meeting the business need.