Pass CCBA Exam Guide

Item tracking methods are techniques to monitor and control the status of items such as issues, defects, changes, or action items. They help to manage and resolve the outstanding issues that have been logged in an issues register. Requirements documentation, requirements analysis, and metrics and KPIs are not techniques for managing and resolving issues. References: BABOK Guide v3, page 387; CCBA Mock Test, question 13

The basis on which the requirements should be prioritized in this context is benefit. This means that the requirements should be ranked or ordered based on their value or impact for the stakeholders or the organization. The benefit of a requirement can be measured or estimated by various criteria such as return on investment, customer satisfaction, competitive advantage, etc.

The other options are incorrect because:

• Option B is incorrect because cost is not the basis on which the requirements should be prioritized in this context, but a factor that should be considered in prioritizing the requirements. Cost is the amount of money or resources required to implement or maintain a requirement. Cost can affect the feasibility or viability of a requirement.
• Option C is incorrect because risk is not the basis on which the requirements should be prioritized in this context, but a factor that should be considered in prioritizing the requirements. Risk is the uncertainty or possibility of a negative or positive outcome or event that may affect a requirement. Risk can affect the urgency or importance of a requirement.
• Option D is incorrect because penalty is not the basis on which the requirements should be prioritized in this context, but a factor that should be considered in prioritizing the requirements. Penalty is the consequence or loss that may occur if a requirement is not met or delivered. Penalty can affect the necessity or desirability of a requirement.

References:

• BABOK Guide v3, section 10.43: Prioritization
• CCBA Exam Questions, question 29

The previous task that could assist the BA in performing the impact analysis is to create requirement relationships. This is because creating requirement relationships is the process of identifying and documenting the connections or associations between different requirements or other elements. Creating requirement relationships can help to understand the dependencies, traceability, composition, generalization, or other types of relationships among the requirements. This can facilitate the impact analysis of a change by showing how it affects other related requirements or elements. The other options are not as helpful or relevant as creating requirement relationships. References:

• BABOK Guide, section 4.3.2: Validate Requirements
• CCBA Practice Test, question 107

 The requirements attribute that the BA should assign to allow cost implications to be assessed is complexity. This is because complexity is a measure of how difficult, intricate, or involved a requirement or a solution is. Complexity can have an impact on the cost of implementing or maintaining a requirement or a solution by affecting the effort, time, resources, or skills needed. Assigning complexity to the requirements can help to estimate and compare the cost implications of different requirements or solutions, especially for a project with financial constraints. The other options are not as relevant or useful as complexity. References:

• BABOK Guide, section 4.2.4: Structure Requirements
• CCBA Practice Test, question 109