Free Practice Questions for IIBA CBAP Exam

 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 of determining the relative importance and urgency of the requirements based on the criteria and preferences of the stakeholders. Prioritizing requirements can help to allocate resources, manage scope, and resolve conflicts. One of the factors that can affect the prioritization of requirements is the dependency, which means that one requirement must be implemented before another requirement can be implemented. In this case, you are correct to move one of the requirements higher in the prioritization because it is needed to be implemented before some of the more important requirements are done. This way, you can ensure that the dependency is satisfied and that the project can deliver the expected value. Ralph is incorrect to rank the requirements based on their level of difficulty, as this is not a relevant criterion for prioritization. The level of difficulty can be considered in the estimation and planning of the project, but not in the prioritization of the requirements. References: BABOK Guide v3, page 52; CBAP / CCBA Certified Business Analysis Study Guide, page 160.

 Voting is a technique of requirements prioritization that involves asking the stakeholders to express their preferences for the requirements using various methods, such as ranking, rating, or allocating points or money. Voting helps to achieve consensus and alignment among the stakeholders and to identify the most important and valuable requirements. In this scenario, the business analyst is using a voting method that assigns play money to the requirements, which reflects the relative importance and benefit of each requirement. The requirements with the highest amount of play money are prioritized over the ones with lower amounts.

References:

BABOK® Guide, p. 55, 376-377

CBAP / CCBA Certified Business Analysis Study Guide, p. 165-166

Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 2, Week 1, Video: “Requirements Prioritization”

 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

 A repository is a centralized place where project requirements are stored and managed throughout the project lifecycle. A repository can be a physical or electronic system that allows business analysts to access, update, and track the status of the requirements. A repository can also facilitate the communication, collaboration, and verification of the requirements among the stakeholders. A repository is not the same as a change management system (A), a project scope statement ©, or a requirements register (D), which are different tools or documents that serve different purposes in project management. References:

IIBA BABOK Guide v3, p. 30, 176, 264

How to Write Project Requirements | Smartsheet, paragraph 3

What is Requirements Management? | IBM, paragraph 1

 A vision statement is a document that defines the business needs, identifies key stakeholders, and describes the positive impact the solution will provide on the key stakeholders. A vision statement is a high-level summary of the purpose, scope, and objectives of the project or initiative. It helps to align the stakeholders’ expectations, communicate the value proposition, and guide the decision making throughout the project lifecycle. A vision statement is one of the key inputs for the enterprise analysis process, which involves defining the business need, assessing the capability gaps, determining the solution approach, defining the solution scope, and defining the business case1234. References: 1: BABOK® Guide v3, section 3.4.1 Define Business Need, page 69 2: CBAP / CCBA Certified Business Analysis Study Guide, chapter 4, page 106 3: Business Analysis Techniques: Developing the Vision, pages 23-24 4: How to Write a Vision Statement for Your Business5

The business analysis approach is a plan that describes how the business analysis activities will be performed, including the deliverables, the team roles, the analysis techniques, the communication methods, the change management process, and the stakeholder engagement strategy. The business analysis approach does not define the requirements for solutions acceptance, which are the criteria that the solution must meet to be accepted by the stakeholders. The requirements for solutions acceptance are part of the solution scope, which is an output of the enterprise analysis tasks, not the business analysis approach. References:

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

[CBAP Certification Study Guide v3.0], Chapter 4: Requirements Life Cycle Management, Section 4.1: Plan Business Analysis Approach, page 4-22

Business Analysis Approach, paragraph 1

 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 top-down estimate is an estimate based on past projects to predict the current cost and/or duration of the current project. It is also called an analogous estimate, as it involves using data from previous, similar projects to estimate activity durations1. Top-down estimates are usually done at the early stages of a project, when there is not enough detail or information available to perform more accurate estimates. They are useful for providing a rough order of magnitude (ROM) or a ballpark figure for the project scope, cost and schedule. Top-down estimates are typically faster and cheaper to produce than bottom-up estimates, but they are also less accurate and reliable23. References: 2: Project Cost Estimation: How to Estimate Project Cost - ProjectManager2 3: 11 Cost Estimating Methods (With Formulas and Examples) | Indeed.com3 1: Understanding the Analogous Estimating Technique | Runn1

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