CCBA Exam Dumps : Certification of Capability in Business Analysis (CCBA)

A tester is the stakeholder who is responsible for verifying released and solution components. A tester is a person who performs testing activities to ensure that the solution meets the quality standards and the requirements. A tester is involved in the allocated requirements to design, execute, and report test cases, as well as to identify and document defects and issues. A tester is different from the project team, which is the group of people who work together to deliver the project objectives; the project manager, who is the person who leads the project team and manages the project scope, schedule, budget, and risks; and the operational support, which is the function that provides the maintenance and support for the solution after it is deployed. References:

CCBA Handbook, page 11

[BABOK Guide], page 13

[Business Analysis for Practitioners: A Practice Guide], page 17

[Business Analysis: The Question and Answer Book], page 11

 According to the Capability in Business Analysis™ (CCBA®) guidelines, one of the tasks that business analysts perform in the requirement elicitation activity is to conduct elicitation sessions, which involves facilitating workshops and other techniques to elicit the requirements from thestakeholders12. During the elicitation sessions, the business analyst should be prepared to handle any issues that may arise, such as scope creep, conflicting opinions, or unclear requirements34. If a stakeholder raises an issue that is outside of the project’s scope, the business analyst should consider the issue’s impact on the project and gain agreement with stakeholders on the next step, such as deferring the issue to a later stage, escalating the issue to the project manager, or revising the scope statement5.

References: The CCBA® learning documents, which can be found on the IIBA website12, describe the various tasks and techniques that a business analyst can use to elicit the requirements from the stakeholders, including the conduct of elicitation sessions and the handling of issues. Additionally, the IIBA Bookstore offers resources that provide further insights into the objectives and best practices for business analysis, including the facilitation of workshops and the management of scope3

According to the CCBA® Handbook, one of the techniques for requirements elicitation is focus group, which is “a facilitated session that brings together a pre-defined group of stakeholders to discuss and provide feedback on a topic” (p. 22). Focus group is a useful technique when you have a large number of stakeholders who share similar characteristics, needs, or interests, and you want to gather their opinions, preferences, or expectations in a structured way. By meeting with a small group of administrative assistants that will serve as representatives for the remaining administrative assistants, you can use the focus group technique to elicit their requirements for the new software. You can also validate the requirements with the larger group of administrative assistants through other techniques, such as surveys or questionnaires. The other options are not correct because:

B. You will need to meet with all of the administrative assistants as part of requirements elicitation is not a feasible or efficient approach, as it would require a lot of time, resources, and coordination to involve 2,400 people in the elicitation process. It would also create challenges for managing and analyzing the requirements data.

C. You can meet with a small group of administrative assistants and assume their requirements are reflective of the remaining group of administrative assistants is not a reliable or valid approach, as it would introduce the risk of missing, misinterpreting, or conflicting requirements from the larger group of administrative assistants. It would also reduce the stakeholder engagement and satisfaction with the solution.

D. You can meet with the administrative assistants’ managers is not a sufficient or representative approach, as it would exclude the direct input from the end users of the new software, who are the administrative assistants. The managers may not have the same level of knowledge, experience, or perspective as the administrative assistants, and may not be able to articulate their requirements accurately or completely. References:

CCBA® Handbook, p. 22

12 Techniques for Requirement Gathering | Indeed.com, section “Focus group”