Certified Business Analysis Professional CBAP Updated Exam

Overlooking a key set of stakeholders can have serious consequences for the project, as they may have different needs, expectations, and perspectives than the existing stakeholders. Their requirements may conflict with or invalidate the ones that have been already elicited and analyzed, leading to rework, delays, and increased costs. Alternatively, they may introduce new requirements that require changes to the project scope, schedule, budget, or quality. Therefore, it is important to identify all relevant stakeholders as early as possible in the business analysis process and to engage them throughout the project lifecycle. References:

CBAP Handbook, page 12, section 2.0 Nine-Steps to Certification, step 3. Enter Your Eligibility Details into the BA Development Log

[BABOK Guide], page 30, section 2.2 Conduct Stakeholder Analysis, task description and output

CBAP/CCBA Study Guide, page 55, section 2.2.3 Stakeholder Analysis, stakeholder identification and analysis techniques

Enterprise analysis is a knowledge area that describes the business analysis activities that take place for an enterprise to identify business opportunities, build a business architecture, determine the optimal project investment path for the enterprise and implement new business and technical solutions1. Enterprise analysis can be triggered by different need generation approaches, such as bottom-up, external drivers, middle management, or top-down2. In this case, the business need stems from external drivers, which are factors outside the organization that influence its performance, such as customers, competitors, regulations, or market trends3. A customer requesting new software for collecting customer information is an example of an external driver that creates a business need for the organization. The organization should conduct enterprise analysis to understand the customer’s requirements, assess the current capabilities and gaps, evaluate the feasibility and risks of the proposed solution, and define the business case and scope for the project. References:

What is Enterprise Analysis: does it differ from Enterprise Architecture?

[Enterprise Analysis - Business Analyst Training]

[External Drivers: Definition & Examples - Video & Lesson Transcript | Study.com]

The business analysis process that ensures that requirements specifications and models meet the necessary standard of quality to allow them to be used effectively to guide further work is verify requirements. According to the BABOK® Guide1, this process involves checking that the requirements are well-defined, clear, consistent, complete, correct, feasible, modifiable, testable, and traceable. It also involves resolving any defects or issues that may affect the quality of the requirements. The purpose of this process is to confirm that the requirements specifications and models accurately reflect the stakeholder needs and expectations, and that they are ready for validation and approval.

The other options are not correct, but rather:

A. Identify constraints and assumptions is a task within the assess capability gaps process, which involves comparing the current and future states of the organization to identify the gaps that must be addressed by a solution.

B. Validate requirements is a process that ensures that the requirements support the delivery of value to the stakeholders and achieve the goals and objectives of the project or initiative. It involves evaluating the alignment, acceptability, and approval of the requirements by the stakeholders.

D. Specify and model requirements is a process that involves defining and representing the requirements in various formats, such as textual, graphical, or tabular. It helps to communicate, analyze, and refine the requirements more effectively.

References:

CBAP® Handbook, page 6, section 4. Review the Exam Blueprint, under Requirements Analysis and Design Definition, task 5.3: Verify Requirements

BABOK® Guide, page 33, section 4.2.3: Verify Requirements

How Do Business Analysts Verify Requirements? (BABOK 6.5)

What Is Requirements Analysis? Process and Techniques

 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