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

The project team should consult with the business owner to discuss possible trade-offs when prioritizing requirements. Trade-offs are compromises or concessions that are made to balance conflicting or competing factors or criteria. Trade-offs can help to resolve disagreements or disputes among stakeholders regarding the relative importance or urgency of requirements. Requirements are conditions or capabilities that a stakeholder needs or wants from a solution.

The other options are incorrect because:

Option A is incorrect because changing the priority of the requirements by performing a ranking is not a collaborative technique, but an analytical technique. Ranking is a method of assigning scores or values to requirements based on predefined criteria or scales. Ranking can help to compare and order requirements according to their significance or relevance for a solution, but it does not involve stakeholder input or feedback.

Option C is incorrect because implementing the requirements that the project team considers important is not a collaborative technique, but an authoritative technique. Authoritative techniques are based on the power or influence of a single person or group over others. Authoritative techniques can help to expedite or simplify the decision-making process, but they may not reflect the consensus or agreement of all stakeholders.

Option D is incorrect because executing the requirements that the business owner identified is not a collaborative technique, but an authoritative technique. Authoritative techniques are based on the power or influence of a single person or group over others. Authoritative techniques can help to expedite or simplify the decision-making process, but they may not reflect the consensus or agreement of all stakeholders.

References:

BABOK Guide v3, section 10.43: Prioritization

CCBA Exam Questions, question 6

The BA can find out which stakeholder has the authority to approve, deny, or defer the change request from the governance approach. The governance approach defines how decisions are made regarding business analysis activities and deliverables. It specifies who are involved in making decisions, what are their roles and responsibilities, what are the criteria and processes for decision making, and how decisions are communicated and documented. The governance approach can help to identify which stakeholder has decision-making authority over change requests. References: : BABOK Guide v3, Section 2.4

The cost of tracing is the factor that takes precedence while determining the requirements traceability approach. Requirements traceability is the ability to track a requirement from its origin to its realization in a solution1. Requirements traceability helps to ensure that the requirements are aligned with the business need, the solution scope, and the test cases. However, requirements traceability also involves effort and resources to establish and maintain the links between requirements and other artifacts. Therefore, the cost of tracing should be balanced with the benefits of traceability, and the level of traceability should be appropriate for the project context and complexity2. The otherfactors, such as number of defects, number of stakeholders, and cost of testing, are not directly related to the requirements traceability approach, although they may influence the decision on how much traceability is needed. References:

1: BABOK® Guide v3, Chapter 6: Requirements Life Cycle Management, Section 6.4: Maintain Requirements

2: Business Analysis Expert Certification, CCBA® | IIBA®

The element of risk assessment that the BA needs to consider is risk tolerance. Risk tolerance is the degree of uncertainty that an organization or a stakeholder is willing to accept in relation to the achievement of its objectives or goals1. Risk tolerance can vary depending on the type, impact, and likelihood of the risk, as well as the stakeholder’s attitude, perception, and preference. The BA should consider the risk tolerance of the organization and the stakeholders when quantifying the probability that the solution will meet their needs and assessing the relevant risks. References: 1: BABOK Guide v3, Section 3.2

 Logistics setup is a technique that defines the physical and technical arrangements for conducting elicitation activities, such as location, time, equipment, and materials1. Logistics setup can help theBA to handle the situation where not everyone could attend the meeting because of their individual dispersed locations, by adjusting the arrangements to accommodate the remote participants, such as using online conferencing tools, sending the agenda and materials in advance, and recording the session for later review2. The other options are not the things that the BA needs to adjust to handle the situation, but rather the things that the BA may have already defined or planned before the elicitation activities. Project stakeholders are the people or groups who have an interest or influence in the project or the solution3. Elicitation scope is a technique that defines the boundaries and sources of information for the elicitation activities. Elicitation technique is a technique that defines the methods and practices for obtaining information from the stakeholders. References:

1: BABOK® Guide v3, p. 50

2: Logistics Setup: Definition, Elements and Examples

3: BABOK® Guide v3, p. 13

: BABOK® Guide v3, p. 51

: BABOK® Guide v3, p. 52

 Requirements management tools provide a means to document traceability and change of requirements and designs. Requirements management tools are software applications that support the documentation, analysis, tracking, prioritization, approval, and change management of requirements4. They can help to establish relationships and dependencies among requirements, solution components, designs, tests, and other artifacts. They can also help to record and monitor changes to requirements and designs, as well as their audit and approval history. References: 4: BABOK Guide v3, Section 9.6

 Requirements architecture is a technique that organizes and structures requirements into a coherent whole, using a combination of text and models1. Requirements architecture can help the BA to model the requirements for the review by showing the relationships, dependencies, and priorities among the requirements2. Requirements architecture can also help the BA to communicate the requirements to the stakeholders in a clear and consistent way3. The other options are not guidelines or tools for modeling the requirements. Current state description is a technique that describes the existing situation or environment of an organization or a stakeholder4. Methodologies and framework are sets of methods, principles, and practices that guide the business analysis work. Domain knowledge is the understanding of a specific subject matter or industry. References:

1: BABOK® Guide v3, p. 388

2: Requirements Architecture: A Framework for Clear Communication

3: Requirements Architecture: The Key to Successful Requirements Management

4: BABOK® Guide v3, p. 390

: BABOK® Guide v3, p. 12

: What is Domain Knowledge and Why is it Important?

The business analyst should assess the impacts of the technical constraints on the project scope, schedule, budget, quality, and risks. The BA should also re-prioritize the requirements based on the new information and the stakeholder needs. This will help the BA to ensure that the project delivers the most value to the business and the customers, while also managing the expectations and addressing the issues caused by the technical constraints.

References: The answer is based on the BABOK® Guide, which is a key resource for the CCBA® certification. Specifically, it relates to the Requirements Analysis and Design Definition knowledge area, where assessing and re-prioritizing requirements are essential tasks for the BA12. It also relates to the Requirements Life Cycle Management knowledge area, where the BA should manage changes to the requirements and communicate them to the stakeholders13.