IIBA Updated CCBA Exam Questions and Answers by carmen

The business analysis task that Shelly is facilitating in this scenario is validate requirements. This task involves ensuring that the requirements align with the business objectives, goals, and vision of the organization, and that they support the delivery of value. Shelly and Thomas are reviewing the requirements to verify that they are consistent, feasible, and acceptable for the stakeholders. The other options are not relevant to this scenario, as they involve defining the criteria for accepting the solution (A), ensuring the quality of the requirements documentation (B), or managing the relationships and expectations of the stakeholders (D). References: CERTIFICATION OF CAPABILITY IN BUSINESS ANALYSIS, Certification of Capability in Business Analysis (CCBA®) - Simplilearn

 The business analysis approach is the methodology and process that will be used to conduct business analysis activities and deliver business analysis outputs. The business analysis approach can be either plan-driven or change-driven, depending on the nature and context of the project. A plan-driven approach is a predictive methodology that follows a sequential and structured process, where the requirements and the solution are fully defined before implementation begins. A change-driven approach is an adaptive methodology that follows an iterative and flexible process, where the requirements and the solution are continuously refined and validated through feedback and collaboration1

The primary inputs to the business analysis approach are:

Organizational process assets: These are the policies, procedures, standards, templates, and tools that are available within the organization and that can influence the selection and execution of the business analysis approach. For example, the organization may have a preferred or mandated methodology, a set of best practices, or a repository of historical data that can guide the business analysis activities2

Expert judgement: This is the knowledge and experience of subject matter experts who can provide guidance and recommendations on the most suitable business analysis approach for the project. For example, the experts may include senior business analysts, project managers, stakeholders, or external consultants who have expertise in the domain, the industry, the technology, or the methodology3

Business need: This is the problem or opportunity that the project aims to address. It defines the gap between the current and desired states of the organization and its capabilities. The business need can influence the choice of the business analysis approach based on factors such as the urgency, complexity, uncertainty, and value of the need4

Penalty of not seizing the opportunity: This is the potential loss or risk that the organization may incur if the project fails to deliver the expected benefits or outcomes. It reflects the importance and priority of the project for the organization and its stakeholders. The penalty of not seizing the opportunity can influence the choice of the business analysis approach based on factors such as the scope, quality, cost, and time of the project.

References: Business Analysis Body of Knowledge (BABOK® Guide), Section 5.1: Plan Business Analysis Approach, 5.1.1: Purpose; Business Analysis Body of Knowledge (BABOK® Guide), Section 5.1: Plan Business Analysis Approach, 5.1.2.1: Organizational Process Assets; Business Analysis Body of Knowledge (BABOK® Guide), Section 5.1: Plan Business Analysis Approach, 5.1.2.2: Expert Judgement; Business Analysis Body of Knowledge (BABOK® Guide), Section 5.1: Plan Business Analysis Approach, 5.1.2.3: Business Need; [Business Analysis Body of Knowledge (BABOK® Guide)], Section 5.1: Plan Business Analysis Approach, 5.1.2.4: Penalty of Not Seizing the Opportunity.

Linked is not a valid relationship type among requirements. Requirements can have different types of relationships, such as derivation, satisfaction, verification, refinement, traceability, dependency, conflict, or overlap1. These relationships can help to analyze the impact, consistency, completeness, and quality of the requirements2. However, linked is not a specific or meaningful term to describe how requirements are related.

The other options are valid relationship types among requirements:

Necessity is a relationship type that indicates that a requirement is essential for achieving a goal or satisfying a need3.

Cover is a relationship type that indicates that a requirement addresses or fulfills a stakeholder need or expectation4.

Subset is a relationship type that indicates that a requirement is a more detailed or specific version of another requirement5.

References:

Relationship Analysis in Requirements Engineering, section “Relationship Types”

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), version 3, chapter 6, section 6.1.4.1

Necessity, section “Description of Change”

Cover, section “Description of Change”

Subset, section “Description of Change”

 Enterprise architecture is a description of the current and future state of an organization in terms of its business processes, information systems, and technology infrastructure. It defines the business requirements, solution scope, and solution requirements for achieving the organization’s vision, goals, and objectives. Enterprise architecture helps to align the business and IT strategies, optimize the use of resources, and enable effective change management12.

The other options are not correct because:

Option A is incorrect. Matrix structure is a type of organizational structure that combines functional and project-based units. It defines the roles, responsibilities, and reporting relationships of the staff members. Matrix structure does not describe the business requirements, solution scope, and solution requirements for an organization3.

Option C is incorrect. Organizational process asset is a term used in project management to refer to any process, policy, plan, procedure, or knowledge base that is specific to and used by an organization. Organizational process assets can help to guide, support, or influence the project activities and outcomes. Organizational process assets do not describe the business requirements, solution scope, and solution requirements for an organization4.

Option D is incorrect. Business need is a problem or opportunity that the organization faces or wants to address. It provides the context and justification for initiating a project or a task. Business need does not describe the solution scope and solution requirements for an organization.

References:

Enterprise Architecture, section “Description of Change”

What is Enterprise Architecture? A Framework for Transformation, section “What is Enterprise Architecture?”

Matrix Structure, section “Description of Change”

Organizational Process Assets, section “Description of Change”

[Business Need], section “Description of Change”