CBAP Exam Dumps - Certified Business Analysis Professional

 A business analysis communications plan is a document that describes how the business analysis information will be communicated to the stakeholders, including the format, frequency, content, and recipients of the communication. A business analysiscommunications plan can help to ensure that the stakeholders are informed, engaged, and satisfied with the business analysis work, and that the business analysis deliverables are validated and approved. A business analysis communications plan is part of the business analysis plan, which is a comprehensive document that covers all aspects of the business analysis approach, activities, and deliverables. References: BABOK Guide v3, page 37; CBAP / CCBA Certified Business Analysis Study Guide, page 75.

Rough order of magnitude (ROM) cost estimating is a process of estimating the costs of the proposed solutions with a high level of uncertainty, usually in the range of -25% to +75%. ROM cost estimating is used to compare the feasibility and affordability of different solutions and to support decision making. ROM cost estimating is not a detailed or accurate process, but rather a quick and approximate way of assessing the costs of the solutions. References: CBAP / CCBA Certified Business Analysis Study Guide, Chapter 6: Requirements Analysis, page 202. Certified Business Analysis Professional (CBAP®) Handbook, page 6.

 A one-to-one interview is the most common type of interview as part of requirements elicitation. A one-to-one interview is a systematic approach for eliciting information from a single person in an informal or formal setting by asking questions and documenting the responses. A one-to-one interview allows the business analyst to establish rapport with the interviewee, probe deeper into their needs and expectations, observe their non-verbal cues, and clarify any ambiguities or inconsistencies. A one-to-one interview is also easier to schedule and conduct than other types of interviews that involve multiple participants, such as many-to-one, many-to-many, or one-to-many. References:

• Requirements Elicitation: Interview Dos and Don’ts, paragraph 1
• Top 10 Most Common Requirements Elicitation Techniques, paragraph 3
• Types of Elicitation Techniques for the Business Analyst, paragraph 2
• What Questions Do I Ask During Requirements Elicitation?, paragraph 1
• Interviews: Requirements Elicitation Technique, paragraph 1

Requirements are dynamic and may change throughout the project life cycle due to various factors, such as changing stakeholder needs, new business opportunities, feedback from testing, or regulatory changes. Business analysis planning and monitoring involves defining the process for managing changes to requirements, including identifying the roles and responsibilities, the approval levels, the change control tools, and the communication methods. The business analyst should be prepared to handle changes to requirements at any time and follow the established change control process. References:

• CBAP® Handbook, page 6, section 2.4. Review the Exam Blueprint
• BABOK® Guide, page 29, section 2.4. Manage Business Analysis Performance
• Tips for Earning a Business Analysis Certification, point 3. Understand the BABOK® Guide

 Scope modeling is a technique that can be used to establish appropriate boundaries for the solution, as it describes the essence of one or more boundaries and places components inside or outside those boundaries. Scope modeling can help to define the scope of control, change, solution, or need for the project. Scope modeling can also help to identify the in-scope and out-of-scope elements, as well as the relationships and dependencies among them. Scope modeling can provide the foundation for understanding the scope of the solution and the value it delivers to the organization12. Scope modeling can be represented as a blend of diagrams, matrices, and textual descriptions, such as context diagrams, use case models, Venn diagrams,etc134. References: 1: Scope modelling in business analysis – The Functional BA1 2: 10.41 Scope Modelling | IIBA®2 3: Business Analysis Scope Modeling Training | Netmind Course3 4: How Should a Business Analyst Define “Project Scope?”4

 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®]

 A business analysis communication plan is a document that describes how the business analyst will communicate with the stakeholders, including the stakeholder groups, communication needs, level of formality, frequency, format, and methods of communication. It is one of the outputs of the business analysis planning and monitoring knowledge area, and it helps to ensure that the stakeholders are informed, engaged, and satisfied with the business analysis process and deliverables. A business analysis communication plan is not the same as a project communication plan, which covers the overall communication needs of the project and is typically created by the project manager. A business analysis communication plan focuses on the specific communication needs related to the business analysis activities and requirements. References:

• IIBA BABOK Guide v3, p. 36, 38, 40, 42
• How to Create a Stakeholder Management Plan Smartsheet
• CBAP 150 Practice Questions Flashcards, Question 5
• How To Create an Effective Stakeholder Communication Plan

 A statement of work (SOW) is a narrative description of the work required for the project. It includes the project objectives, scope, deliverables, schedule, budget, quality standards, and acceptance criteria. It also defines the roles and responsibilities of the project team and the client, and the terms and conditions of the contract. A SOW is a formal document that establishes the agreement between the project provider and the project customer, and that guides the project execution and control12.

The other options are not correct. A. A contract work breakdown structure (CWBS) is a hierarchical decomposition of the contract deliverables into smaller and manageable components. It helps to define the scope, cost, and schedule of the contract, and to monitor and report the contract performance3. B. A work breakdown structure (WBS) is a hierarchical decomposition of the project work into smaller and manageable components. It helps to define the scope, cost, and schedule of the project, and to assign the work packages to the project team4. C. A contract statement of work (CSOW) is a document that describes the work to be performed by a contractor or a vendor under a contract. It is similar to a SOW, but it is more specific and detailed, and it is used for procurement purposes5. References:

• What is a Statement of Work (SOW)? - Definition from WhatIs.com
• Statement of Work: Definition & Examples - ProjectManager
• Contract Work Breakdown Structure (CWBS) - AcqNotes
• Work Breakdown Structure (WBS) - Project Management Institute
• Contract Statement of Work (CSOW) - AcqNotes