CBAP Exam Dumps : Certified Business Analysis Professional

 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

Prioritizing requirements is a process that helps business analysts and stakeholders to rank the requirements according to their importance, value, urgency, and dependency. Prioritizing requirements helps to ensure that the most critical requirements are addressed first, and that the available resources are allocated effectively. Prioritizing requirements also helps to manage the scope, schedule, and budget of the project, and to deal with changes and uncertainties. Prioritizing requirements is not only about determining the cost or the schedule of each requirement, but also about understanding the impact and the benefit of each requirement on the business need and the solution. Prioritizing requirements is not only about identifying the risks associated with each requirement, but also about mitigating or avoiding those risks by choosing the best solution option. References:

[A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 402, section 10.31.3.11

Why Prioritise Requirements – How to do it and Why it is Critical to Project Success – BusinessAnalystMentor.com, paragraph 1

Why You Should Prioritize Requirements - ArgonDigital, paragraph 1

What Is Requirements Prioritization? Definition & Examples - airfocus, paragraph 1

Business analysts : How to prioritize requirements - Adaptive US, paragraph 1

The all out approach is a timeboxing or budgeting technique that involves excluding all the requirements for a start and then including the ones that can be implemented within the constrained time or budget. Henry is using this approach by removing the requirements from the allowed list until he meets the budget limit. This is different from the all in approach, which involves including all the requirements necessary for the solution and then removing or postponing the ones that will cause the project to exceed the deadline or budget. The parametric approach is a cost estimation technique that uses statistical relationships between historical data and other variables. The selective approach is a prioritization technique that involves ranking the requirements based on their value and urgency. References:

CBAP Certification Study Guide v3.0, p. 223

BABOK Guide v3, p. 156