CCBA Questions Bank

 An organizational process asset is a term that describes the organizational policies, procedures, forms, and methodologies that the business analyst is to follow. These are the established practices and guidelines that the organization has developed and maintained over time, and they provide a framework for conducting business analysis activities. Organizational process assets may include templates, standards, checklists, tools, best practices, lessons learned, and other resources that can help the business analyst perform their tasks more efficiently and effectively.

References: The information is verified as per the BABOK® Guide and related IIBA resources, which outline the standards and practices for business analysis. The BABOK® Guide is a key resource for understanding business analysis inputs and outputs123. You can also find some useful resources and sample questions from other sources

Before requirements can be approved to be managed, they must be verified and validated to ensure that they are aligned with the solution scope, which is the set of capabilities and conditions that the solution must satisfy to meet the business need12. Requirements that do not support the solution scope may introduce unnecessary complexity, cost, or risk to the project, or may not deliver the expected value to the stakeholders. Therefore, it is important to check that the requirements are consistent, complete, correct, feasible, and testable before approving them to be managed3. References:

• 1: BABOK® Guide, Version 3.0, p. 33
• 2: Business Analysis Expert Certification, CCBA® | IIBA®
• 3: BABOK® Guide, Version 3.0, p. 41

 According to the web search results12, problem tracking is a process of identifying and managing the causes of incidents on an IT service, and it is a core component of ITSM frameworks. Problem tracking is not the same as issue tracking, which is a way of recording and tracking the status of customer cases, tickets, or concerns3. Problem tracking is also not the same as bug tracking, which is the process of logging and monitoring bugs or errors during software testing4.

The implementation subject matter expert is not a stakeholder who participates in the prioritization of requirements, because they are not directly affected by the business need or the solution. The project team, the domain subject matter expert, and the project manager are all stakeholders who have a vested interest in the outcome of the project and the value of the solution, and therefore they should be involved in the prioritization of requirements. References:

• Business Analysis Expert Certification, CCBA® | IIBA®, section “Who can Become a CCBA?”
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), section 4.2.5 “Prioritize Requirements”