IIBA Updated CBAP Exam Questions and Answers by deen

Scenario and uses cases and user stories are conduct stakeholder analysis techniques that identify stakeholder roles that may serve as a useful starting point for identifying actors and roles. These techniques describe how stakeholders interact with the solution or the business process, and what their goals, needs, and expectations are. By creating scenarios and use cases and user stories, the business analyst can identify the primary and secondary stakeholders, as well as their roles and responsibilities. These techniques can also help to elicit, validate, and prioritize the requirements, as well as to communicateand collaborate with the stakeholders1234. References: 1: Scenarios, Use Cases, and User Stories1 2: Business Analysis Techniques: Eliciting Information and Collaborating with Stakeholders2 3: Use Cases and Scenarios3 4: User Stories4

The solution scope definition is a document that describes the features and functions of the solution that will address the business need and deliver the expected benefits. It also defines the boundaries and assumptions of the solution, as well as the criteria for its acceptance and evaluation. The solution scope definition should include the following elements:

• Solution vision: A brief statement that summarizes the purpose, value proposition, and target audience of the solution.
• Solution objectives: A list of measurable and achievable goals that the solution aims to accomplish, aligned with the business goals and objectives.
• Solution requirements: A detailed and specific description of the stakeholder and solution requirements that define the scope and functionality of the solution, organized by categories, types, and priorities.
• Solution constraints: A list of factors that limit the options or performance of the solution, such as technical, legal, regulatory, or organizational constraints.
• Technical dependencies: A list of relationships or interactions between the solution and other systems, components, or technologies that affect the solution’s design, development, or implementation.
• Solution risks: A list of potential threats or uncertainties that may affect the solution’s success, along with their probability, impact, and mitigation strategies.
• Solution scope statement: A concise statement that defines what is in and out of scope for the solution, and clarifies any ambiguities or conflicts among the solution requirements.

The solution scope definition does not include the business case (A), which is a separate document that justifies the need for the solution and analyzes its costs and benefits. The solution scope definition also does not include the elicitation techniques ©, which are themethods or tools used to gather information from the stakeholders and discover the requirements. The solution scope definition also does not include the organization readiness assessment (D), which is an analysis of the organization’s ability and willingness to adopt the solution and manage the change.

References:

• [A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 30, section 3.11
• Solution Scope – An Insight - Modern Analyst, paragraphs 2-3
• Scoping a Solution | Microsoft Solutions Framework Essentials … - Flylib, paragraph 1
• [Solution Scope vs. Project Scope - Enfocus Solutions Inc], paragraph 2
• [How to Write Project Requirements | Smartsheet], paragraph 3

 A business analysis plan is a document that describes the scope of work, the deliverable Work Breakdown Structure (WBS), the activity list, and estimates for the business analysis activities. It also includes the business analysis approach, the roles and responsibilities of the business analyst and other stakeholders, the communication plan, the requirements management plan, the change management plan, and the risk management plan12. Abusiness analysis plan is an important input for the business analysis execution and monitoring process, as it helps to guide and control the business analysis work, and to ensure that the business analysis deliverables meet the quality standards and stakeholder expectations3.

The other options are not correct. A project management plan is a document that describes how the project will be executed, monitored, and controlled. It covers the project scope, schedule, cost, quality, resources, communication, risk, procurement, and stakeholder management. An implementation plan is a document that describes how the solution will be deployed, transitioned, and integrated into the business operations. It covers the implementation strategy, schedule, resources, tasks, roles, responsibilities, risks, and issues. A requirements management plan is a document that describes how the requirements will be elicited, analyzed, documented, validated, verified, prioritized, traced, and maintained throughout the project lifecycle. It is a component of the business analysis plan, not a separate document. References:

• Business Analysis Plan - IIBA®
• Business Analysis Planning and Monitoring - IIBA®
• Business Analysis Execution and Monitoring - IIBA®
• [Project Management Plan - PMI]
• [Implementation Plan - PMI]
• [Requirements Management Plan - IIBA®]

 Business or technical risk is a requirements prioritization approach that involves ranking the requirements based on the potential negative consequences or uncertainties associated with their implementation or non-implementation. This approach can help to identify and mitigate the most critical risks early in the project and reduce the likelihood of project failure. Business or technical risk can be assessed by considering factors such as the impact on the business value, the feasibility of the solution, the complexity of the requirements, the dependencies among the requirements, the volatility of the requirements, and the stakeholder satisfaction. Business or technical risk is one of the common criteria for requirements prioritization, as it helps to balance the benefits and costs of the requirements1234. References: 1: Requirement prioritization3 2: The Ultimate Guide to Requirements Prioritization4 3: Business Analysis Techniques: Prioritizing Requirements5 4: Requirements Prioritization: How to Prioritize Requirements