Free IIBA CBAP Practice Exam with Questions & Answers | Set: 15

 A regulator is not a stakeholder that is considered when completing the business analysis planning and monitoring task to determine a business analysis approach. A regulator is an external entity that imposes rules, standards, or guidelines that the organization and the solution must comply with. A regulator is not directly involved in the business analysis process, but rather in the governance and validation of the solution. Therefore, a regulator does not influence the choice of the business analysis approach, which is based on the characteristics and needs of the project and the organization.

The other options are stakeholders that are considered when completing the business analysis planning and monitoring task to determine a business analysis approach. A tester is a stakeholder who verifies and validates the quality and functionality of the solution. A project manager is a stakeholder who oversees and coordinates the project activities, resources, and deliverables. A functional manager is a stakeholder who manages a specific business function or department, such as finance, marketing, or human resources. These stakeholders have different roles, responsibilities, expectations, and interests in the business analysis process, and they may affect or be affected by the choice of the business analysis approach. References:

BABOK® Guide, p. 29, 32, 66

CBAP / CCBA Certified Business Analysis Study Guide, p. 45, 48, 133

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

Writing the business case is a process of documenting the justification for initiating a project or a solution, based on the estimated costs, benefits, and risks. The inputs to this process are the business need, the assumptions and constraints, the stakeholder concerns, and the solution scope. The business need defines the problem or opportunity that the project or solution will address. The assumptions and constraints are the factors that affect the feasibility and viability of the project or solution. The stakeholder concerns are the expectations, issues, or interests of the stakeholders that may influence the project or solution. The solution scope defines the features and functions of the product or service that will meet the business need and the stakeholder concerns. Requirements verification is not an input to this process, but rather an output of the verify requirements process, which is part of the requirements analysis and design definition knowledge area. References: BABOK Guide v3, page 25; CBAP / CCBA Certified Business Analysis Study Guide, page 69.

 Document analysis is a requirements elicitation technique that examines the available information, documentation, records, and history of a solution, organization, or cause to identify relevant information to the current business analysis duties. Document analysis helps the business analyst to understand the existing processes, policies, standards, regulations, and systems that may affect the project or the solution. Document analysis also helps to discover the implicit, hidden, or undocumented requirements that may not be easily obtained from other sources. Document analysis can be done using various types of documents, such as business plans, contracts, manuals, reports, diagrams, models, or logs. Document analysis is different from benchmarking, which is a technique that compares the performance or practices of an organization or a solution with those of other organizations or solutions. Document analysis is also different from dataflow diagrams, which are graphical models that show how data moves through a system or a process. Document analysis is not requirements elicitation, which is a general term for the process of gathering and discovering the requirements from various sources and stakeholders. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 4: Elicitation and Collaboration, page 181-182.

[Requirements Elicitation in Software Engineering Complete Guide …, paragraph 3

Elicitation Technique Guide | Info-Tech Research Group, paragraph 1

Requirements elicitation techniques: a systematic literature review …, paragraph 1

 According to the BABOK® Guide, one of the tasks of defining the business need is to review the requirements stated documentation and ensure that it reflects the actual business requirements, not a description of the solutions. This is important because the business need should be based on the underlying problem or opportunity, not on a predetermined solution. The other options are not relevant to this task. References: BABOK® Guide, v3, p. 30; CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, p. 36.

 A test plan is a document that describes the scope, objectives, strategy, and activities of testing a software product or system. A test plan is mandatory in most software development projects because it ensures that the software meets the quality standards and requirements of the stakeholders. A test plan also helps to identify and mitigate the risks, defects, and issues that may affect the software functionality, performance, usability, and security. A test plan is different from a communication management plan, which is a document that describes how the project information will be communicated to the stakeholders. A test plan is also different from a disaster recovery plan, which is a document that describes how the project will resume its operations in the event of a disaster or emergency. A test plan is not a procurement plan, which is a document that describes how the project will acquire the goods and services needed from external sources. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 9: Solution Assessment and Validation, page 329-330.

How to write a software requirement document (with template), paragraph 6

These testing methods should be mandatory for any software, paragraph 1

Software Testing Plan - Tutorialspoint, paragraph 1

 Verify scope is a process to determine the completeness of the project work and to gain the customer’s acceptance to move the project forward. Verify scope involves reviewing the deliverables and comparing them with the requirements and the scope baseline. It also involves obtaining the formal acceptance of the deliverables from the customer or sponsor. Verify scope helps to ensure that the project meets the expectations and needs of the customer or sponsor, and to avoid scope creep or rework12. Phase gate review is a process to evaluate the progress and performance of the project at predefined points or milestones. Phase gate review involves assessing the deliverables, risks, issues, and resources of the project against the criteria and objectives of each phase. It also involves deciding whether to continue, terminate, or modify the project. Phase gate review helps to ensure that the project is aligned with the business strategy and value, and to control the quality and scope of the project13. Inspection of key results is a process to measure and evaluate the quality and effectiveness of the project work and deliverables. Inspection of key results involves checking the work and deliverables for defects, errors, or deviations from the standards and specifications. It also involves identifying and implementing corrective actions to improve the quality and effectiveness of the work and deliverables. Inspection of key results helps to ensure that the project meets the quality requirements and standards, and to prevent or reduce the cost of poor quality14. Quality control is a process to monitor and control the quality of the project work and deliverables. Quality control involves performing quality audits, inspections, tests, and measurements to verify that the work and deliverables conform to the quality requirements and standards. It also involves identifying and implementing quality improvements to enhance the quality of the work and deliverables. Quality control helps to ensure that the project satisfies the customer or sponsor expectations and needs, and to increase the customer or sponsor satisfaction1 . References: CBAP® Handbook, CBAP® Exam Prep Study Guide, Project Management Institute, Inspection of Key Results - iiba.org, [Quality Control - iiba.org]

 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 analysis communications 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.

An independent task is a task that does not rely on other activities, and no other activities rely on this task completing. An independent task can be performed at any time during the project, as long as it meets the project objectives and requirements. An independent task has no dependencies or constraints with other tasks. An analysis task is a task that involves examining, evaluating, and interpreting information to identify and understand the problem, need, or opportunity. An analysis task may rely on other activities, such as elicitation, documentation, or validation, and other activities may rely on this task completing, such as design, development, or testing. An analysis task may have dependencies or constraints with other tasks. A predecessor task is a task that must be completed before another task can start or finish. A predecessor task has a logical or sequential relationship with another task, which is called a successor task. A predecessor task may affect the start or end date, duration, or resources of the successor task. A dependent task is a task that relies on another task to start or finish. A dependent task has a logical or sequential relationship with another task, which is called a predecessor task. A dependent task may be affected by the start or end date, duration, or resources of the predecessor task. References: CBAP® Handbook, CBAP® Exam Prep Study Guide, Project Management Institute

 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