CBAP Leak Questions

Change requests are more likely to occur in the early stages of a project, when the requirements are being elicited, analyzed, and validated. During this time, stakeholders may discover new needs, identify gaps, or revise their expectations. Change requests may also arise due to changes in the business environment, such as new regulations, market trends, or competitor actions. Change requests are less frequent in the later stages of a project, when the requirements are more stable and the solution is being designed, developed, and tested. References:

A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3, Chapter 4: Requirements Life Cycle Management, Section 4.5: Manage Changes1

CBAP Certification Study Guide v3.0, Chapter 4: Requirements Life Cycle Management, Section 4.5: Manage Changes2

The solution scope definition is a document that describes the features and functions of the solution that will address the business need and deliver the expected benefits. It also defines the boundaries and assumptions of the solution, as well as the criteria for its acceptance and evaluation. The solution scope definition should include the following elements:

Solution vision: A brief statement that summarizes the purpose, value proposition, and target audience of the solution.

Solution objectives: A list of measurable and achievable goals that the solution aims to accomplish, aligned with the business goals and objectives.

Solution requirements: A detailed and specific description of the stakeholder and solution requirements that define the scope and functionality of the solution, organized by categories, types, and priorities.

Solution constraints: A list of factors that limit the options or performance of the solution, such as technical, legal, regulatory, or organizational constraints.

Technical dependencies: A list of relationships or interactions between the solution and other systems, components, or technologies that affect the solution’s design, development, or implementation.

Solution risks: A list of potential threats or uncertainties that may affect the solution’s success, along with their probability, impact, and mitigation strategies.

Solution scope statement: A concise statement that defines what is in and out of scope for the solution, and clarifies any ambiguities or conflicts among the solution requirements.

The solution scope definition does not include the business case (A), which is a separate document that justifies the need for the solution and analyzes its costs and benefits. The solution scope definition also does not include the elicitation techniques ©, which are the methods or tools used to gather information from the stakeholders and discover the requirements. The solution scope definition also does not include the organization readiness assessment (D), which is an analysis of the organization’s ability and willingness to adopt the solution and manage the change.

References:

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

Solution Scope – An Insight - Modern Analyst, paragraphs 2-3

Scoping a Solution | Microsoft Solutions Framework Essentials … - Flylib, paragraph 1

[Solution Scope vs. Project Scope - Enfocus Solutions Inc], paragraph 2

[How to Write Project Requirements | Smartsheet], paragraph 3

Stakeholders are individuals or groups who have an interest in the outcome of a project and can influence its success. Stakeholders can be classified into different categories based on their roles, responsibilities, and perspectives. One common way to categorize stakeholders is by using the RACI matrix, which stands for Responsible, Accountable, Consulted, and Informed. According to this matrix, the following stakeholders participate in the prioritization of requirements:

Project team: Responsible for delivering the solution that meets the requirements. They are directly involved in the prioritization process and provide input on the feasibility, effort, and risk of each requirement.

Domain subject matter expert: Consulted for their expertise and knowledge of the business domain and the needs of the end users. They provide input on the importance, value, and urgency of each requirement.

Project manager: Accountable for the overall success of the project and the alignment of the requirements with the project scope, schedule, and budget. They facilitate the prioritization process and ensure that the stakeholders reach a consensus on the priority levels.

The implementation subject matter expert is not a stakeholder who participates in the prioritization of requirements. They are Informed of the prioritized requirements and the rationale behind them, but they do not provide input or influence the prioritization process. They are responsible for implementing the solution according to the requirements and ensuring that it meets the quality standards and specifications. References:

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

Five Requirements Prioritization Methods - Business Analyst Articles …

What Is Requirements Prioritization? Definition & Examples - airfocus

Business analysts : How to prioritize requirements - Adaptive US

[5 Popular Requirements Prioritisation Techniques]

 According to the BABOK® Guide, conflicts among stakeholders are inevitable and must be resolved before formal approval of the requirements can be obtained. The business analyst is responsible for facilitating the resolution of conflicts by using various techniques such as problem-solving, negotiation, or escalation. The business analyst should not make the decision for the stakeholders, nor should the decision be based on seniority or deferred until later. References: BABOK® Guide v3, section 4.5.5, page 142; CBAP® Handbook, section 4.4, page 6.