A baseline schedule is derived from a schedule model to meet the project execution plan and

achieve management approval for use as a baseline. A schedule model is a representation of the

project activities, durations, dependencies, and resources that shows how the project will be

executed over time. A baseline schedule is a specific version of the schedule model that is approved

and frozen as a reference point for measuring and controlling the project progress and performance.

A baseline schedule reflects the agreed-upon scope, cost, and schedule of the project and serves as a

basis for comparison and change management. Reference: CBAP / CCBA Certified Business Analysis

Study Guide, chapter 6, page 234; CBAP Sample Questions,

:

According to the BABOK Guide, a change-driven approach to business analysis is characterized by

frequent delivery of value to stakeholders, iterative planning and feedback, and adaptive responses

to changing needs and priorities. In such an approach, communications are managed by focusing

more on the frequency of communication and using face-to-face channels as much as possible. This

helps to ensure that information is shared quickly and effectively, and that feedback loops are

established and maintained. Formal communications are less emphasized in a change-driven

approach, as they may slow down the delivery process and introduce unnecessary overhead. Ad hoc

communications are not sufficient for managing change-driven projects, as they may lead to

inconsistency, confusion, and missed information. Reference:

BABOK Guide, section 2.5.3, page 35

How to create a business analysis communication plan, paragraph 2

CBAP/CCBA/ECBA Certification Practice Test,

A class model is a technique to represent the structure and behavior of the entities within a solution

domain. It shows the attributes, operations, and relationships of the classes that define the entities.

A class is a category or type of entity that has common characteristics and can perform certain

functions. A class model helps to identify the entities, their properties, their behaviors, and their

interactions for a solution. Entity Relationship is a technique to represent the data and information

requirements of a solution. It shows the entities, attributes, and relationships of the data and

information. An entity is a thing or object of interest that can be uniquely identified and has

attributes that describe its properties. An entity relationship model helps to identify the data and

information, their characteristics, their associations, and their constraints for a solution. Data

dictionary is a technique to define and document the data and information elements of a solution. It

provides a detailed description of each data and information element, such as its name, definition,

format, type, source, owner, and usage. A data dictionary helps to standardize and clarify the data

and information, their meaning, their structure, and their quality for a solution. CRUD matrix is a

technique to analyze the alignment of the data and information elements with the business

processes or functions of a solution. It shows the data and information elements and the business

processes or functions that create, read, update, or delete them. A CRUD matrix helps to identify the

data and information, their lifecycle, their dependencies, and their gaps for a

solution. Reference: Class Model - iiba.org, Entity Relationship - iiba.org, Data Dictionary -

iiba.org, CRUD Matrix - iiba.org

The project scope statement, an output of the define scope process, does document the process and

criteria for accepting completed products. The project scope statement is a detailed description of

the project scope, which includes the project objectives, deliverables, requirements, boundaries,

assumptions, and constraints. The project scope statement also defines the acceptance criteria,

which are the standards or measures that must be met or satisfied by the products, services, or

results of the project. The acceptance criteria help to ensure that the customer’s needs and

expectations are met and that the project quality is achieved. The project scope statement is a key

input for developing the work breakdown structure, the project schedule, the project budget, and

the project quality plan. Reference: [IIBA BABOK Guide v3], section 5.1.2, page 162; [CBAP / CCBA

Certified Business Analysis Study Guide], chapter 6, page 233; CBAP Sample Questions,

The stakeholders and the BA need to measure benefits, penalties, and costs to determine if the

solution is providing expected value and ensure the accuracy of the measurements. Benefits are the

positive outcomes or value that the solution delivers to the stakeholders or the organization.

Penalties are the negative consequences or costs that the solution may incur if it fails to meet the

requirements or expectations. Costs are the resources or expenses that are required to implement,

operate, and maintain the solution. By measuring benefits, penalties, and costs, the stakeholders and

the BA can assess the return on investment (ROI), the net present value (NPV), and the break-even

point (BEP) of the solution, and compare them with the expected or planned values. This can help to

evaluate the effectiveness, efficiency, and feasibility of the solution, and to identify any gaps, issues,

or opportunities for improvement. Strategy, solution, and scope are not the best options to measure,

because they are either too general, too abstract, or not directly related to the value of the

solution. Reference:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 8: Solution Evaluation,

page 337

Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 8: Solution Evaluation,

section 8.2: Analyze Performance Measures, page 153

Business Analysis Professional Resources, IIBA Resource Collection, Business Analysis Body of

Knowledge (BABOK) Guide

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Skillsoft Book, Chapter 8: Solution

Evaluation, page 337

Decision analysis is a business analysis technique that involves evaluating the feasibility, benefits,

risks, and impacts of various options and selecting the best one based on predefined criteria and

stakeholder p

. In this scenario, the business analyst is considering using decision analysis

to rate the available methodologies against the organizational needs and objectives, and to choose

the most suitable one for the business analysis approach. Decision analysis can help the business

analyst to align the business analysis activities with the project and enterprise goals, and to optimize

the value delivery of the solution. Reference:

BABOK® Guide, p. 66-67

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

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

Analysis Planning and Monitoring”

Variance analysis is the process of comparing the planned project results with the actual project

results and identifying the causes and impacts of any deviations. Variance analysis helps project

managers to monitor and control the project performance, identify and mitigate risks, and

implement corrective actions or changes if needed. Variance analysis can be applied to various

aspects of the project, such as scope, schedule, cost, quality, and resources. Reference:

A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter

4.5.3, p. 123

Planned vs. Actual Progress Explained - SmartPM

Assessing capability gaps is a task of enterprise analysis that involves analyzing the current state of

the organization and comparing it with the desired future state. The purpose of this task is to identify

the new capabilities that the organization needs to acquire or enhance in order to meet the business

need and achieve the organizational goals and objectives. These new capabilities can be related to

processes, systems, people, or resources. Assessing capability gaps can help to determine the scope

and feasibility of the solution, as well as the risks and benefits associated with it. Reference: BABOK

Guide v3, page 25; CBAP / CCBA Certified Business Analysis Study Guide, page 69.

The work breakdown structure (WBS) is not an element of the solution scope, but rather a project

management tool that decomposes the project scope into manageable deliverables and tasks. The

WBS is created after the solution scope is defined and approved, and it helps to plan, monitor, and

control the project execution.

The other options are elements of the solution scope, which are:

B . Implementation approach, which describes how the solution will be delivered, such as the

methodology, the phases, the roles and responsibilities, and the quality measures.

C . Solution scope definition, which describes what the solution is, what it does, and what it does not

do, in terms of the features, functions, and characteristics that address the business need.

D . Dependencies, which describe the relationships and interactions between the solution and other

internal or external factors, such as other projects, systems, processes, or stakeholders.

Reference:

CBAP® Handbook, page 15, section 4.1.2.3

BABOK® Guide, page 32, section 3.2.3

Solution Scope – An Insight

How To Write a Project Scope in 5 Steps (With Example)