CCBA Exam Dumps - IIBA Certification of Capability in Business Analysis Questions and Answers

According to the BABOK® Guide, a requirement is a usable representation of a need. The level of detail and formality of the requirement depends on the context and the audience of the requirement. The goal is to communicate the requirement effectively, not to adhere to a rigid format or level of detail1.

Option A is incorrect because not all requirements need to have technical, business, functional, and non-functional attributes. Some requirements may be more relevant to one or more of these aspects than others.

Option C is incorrect because the organizational process assets are not the only factor that determines the level of detail of the requirements. The stakeholder needs, preferences, and expectations also play a role.

Option D is incorrect because the work package level of WBS is not necessarily the same as the requirement level. The WBS is a project management tool that decomposes the project scope into manageable components, while the requirements describe the needs and expectations of the stakeholders. The WBS and the requirements may not have a one-to-one correspondence.

A domain subject matter expert is a stakeholder who has extensive knowledge and experience in the business area or problem domain that is relevant to the project. They provide valuable insights and information to the business analyst and help to define and validate the requirements and the solution. Adam, who is steeped in knowledge regarding the project’s purpose, is likely to be a domain subject matter expert.

References: The information is aligned with the competencies and knowledge areas defined in the Business Analysis Body of Knowledge® (BABOK® Guide) and the Certification of Capability in Business Analysis™ (CCBA®) as provided by the International Institute of Business Analysis (IIBA®). For detailed references, please consult the CCBA® guide1 and the BABOK® Guide2 available through the IIBA® website and bookstore3. You can also find some useful resources and sample questions from other sources4.

 The allocation of requirements is not an input to the solution scope definition, but a task that will use the solution scope as an input. The allocation of requirements is the process of assigning the requirements to solution components, such as features, functions, modules, etc. The allocation of requirements helps to ensure that the solution components are aligned with the requirements and that the requirements are traceable throughout the project lifecycle. The other options are correct inputs to the solution scope definition, as they provide the information and guidance needed to define the boundaries and characteristics of the solution that will address the business problem or opportunity. The required capability describes what the solution must be able to do to meet the stakeholder needs. The assumptions and constraints identify the factors that affect the feasibility, desirability, or viability of the solution. The business need defines the problem or opportunity that the solution aims to resolve or exploit. References:

• Solution Scope – An Insight
• BABOK Chapter 7: Requirements Analysis and Design Definition
• The quick guide to defining project scope—in 8 steps

A business analysis communications plan is a document that describes how, when, and by whom information about the business analysis activities will be delivered to the stakeholders. It defines the communication goals, the communication requirements, the communication methods, the communication responsibilities, and the communication protocols for the business analysis process. A business analysis communications plan helps to ensure that the stakeholders are informed, engaged, and satisfied with the business analysis deliverables and outcomes12.

The other options are not correct because:

• A stakeholder management plan is a document that describes how the stakeholders will be identified, analyzed, engaged, and managed throughout the business analysis process. It defines the stakeholder roles, interests, expectations, influence, and communication preferences3.
• A business analysis plan is a document that describes how the business analysis activities will be planned, conducted, monitored, and controlled. It defines the business analysis approach, the business analysis scope, the business analysis tasks, the business analysis deliverables, the business analysis schedule, and the business analysis resources4.
• A communications management plan is a document that describes how the project communications will be planned, structured, monitored, and controlled. It defines the project communication goals, the project communication requirements, the project communication methods, the project communication responsibilities, and the project communication protocols5.

References:

• Business Analysis Expert Certification, CCBA® | IIBA®, section “BABOK® Guide v3”, chapter 2, section 2.5.5
• How to create a business analysis communication plan - Lucidchart, section “What is a business analysis communication plan?”
• Stakeholder Management Plan, section “Description of Change”
• Business Analysis Plan, section “Description of Change”
• Communications Management Plan, section “Description of Change”

According to the BABOK® Guide, Version 3.0, the business analysis approach is the set of processes, activities, techniques, deliverables, and roles that are tailored to suit the specific needs and context of a change initiative1. The business analysis approach should be defined in collaboration with the key stakeholders, such as the project manager, the sponsor, the solution owner, and the subject matter experts2. Working with the appropriate stakeholders to determine how the business analysis work should be completed is the best action to take to begin business analysis, as it ensures that the approach is aligned with the project objectives, scope, constraints, and stakeholder expectations3. References:

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

 Customer satisfaction is a subjective requirement that may vary depending on the customer’s expectations, preferences, and perceptions. It is not a measurable or testable requirement and therefore it is difficult to verify and validate. Subjective requirements entail a high level of risk of being successfully accomplished, as they may not be clearly understood, agreed upon, or met by the project team and stakeholders. To reduce this risk, the business analyst should work with the customer and other stakeholders to define more specific, objective, and measurable requirements that reflect the customer’s needs and expectations for the project deliverable. References:

• Business Analysis Expert Certification, CCBA® | IIBA®, section “CCBA Competencies”
• A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), version 3, section 4.2 “Plan Business Analysis Approach” and section 5.1 “Prepare for Elicitation”