IIBA Updated CCBA Exam Questions and Answers by ava-mae

Based on the stakeholder matrix, suppliers are categorized as having high impact but low influence. This suggests that while they are significantly affected by the project, they do not have much control over it. Therefore, the best approach is to keep them well-informed and show interest in their needs to maintain a positive relationship and ensure their requirements are met.

References: The answer aligns with the best practices in stakeholder engagement as per the Capability in Business Analysis™ (CCBA®) guidelines, which recommend tailoring communication strategies to the stakeholders’ level of impact and influence to effectively manage their expectations and contributions to the project. The CCBA® resources available on the IIBA website provide further insights into effective stakeholder engagement strategies.

 In an iterative development process, requirements should be granular. This means they are broken down into small, manageable pieces that can be implemented incrementally. Granular requirements allow for flexibility and adjustments as the project progresses through its iterations, facilitating better response to change and more accurate estimations for each piece of work.

References: The IIBA’s Core Business Analysis Certification Handbook outlines the iterative approach and emphasizes the importance of granular requirements in such processes1. Additionally, the AcqNotes website provides a clear definition of the requirements development steps, which supports the need for granularity in iterative processes2.

Use cases and scenarios are techniques that allow the BA to model the requirements based on the user roles, functionality, and interaction with the solution. Use cases describe the goals, actions, and outcomes of the users in relation to the solution, while scenarios provide examples of how the use cases can be executed in specific situations. Use cases and scenarios help to illustrate the behavior and functionality of the solution from the user’s perspective, as well as the potential variations and exceptions.

References: The answer and explanation are consistent with the CCBA® Handbook and the IIBA® website, which provide the details and best practices for the use cases and scenarios techniques as part of the business analysis process12. The CCBA® resources also describe the types and formats of models that can be used to specify and model requirements, such as use case models and scenario models

Atomic characteristics of requirements ensure that each requirement is self-contained and can be understood without the need to reference other requirements. This means that the requirement is complete and provides enough detail for understanding on its own. It is a key quality attribute in business analysis to ensure clarity and prevent misunderstanding or ambiguity.

References: The concept of atomic characteristics in requirements is covered in the CCBA certification materials, which emphasize the importance of clear, concise, and independent requirements as part of effective business analysis practices123.