Stakeholder requirements describe the needs of those participating in or impacted by business

analysis activities. These requirements focus on ensuring that the perspectives and needs of all

stakeholders are considered and integrated into the solution. Stakeholder requirements are essential

for understanding the context of the business needs and for defining the criteria for the success of

the solution. Reference: The information is verified as per the Business Analysis Learning documents,

specifically the BABOK Guide, which outlines the types of requirements including Business,

Stakeholder, Solution, and Transition Requirements1.

When a business analyst ensures that a set of requirements is developed with enough detail to be

usable by a particular stakeholder, they are performing the activity of verifying requirements.

Verification of requirements involves ensuring that the requirements or designs have been

developed in enough detail, are internally consistent, and are of high quality. This process is crucial

for making sure that the requirements are sufficiently detailed and clear for stakeholders who will be

using them to guide further work, including development and implementation of the solution .

Reference: BABOK Guide v3, Chapter 7.2: Verify Requirements

A business analyst (BA) aims to improve the efficiency and effectiveness of business operations.

Simplifying the work people perform can lead to streamlined processes, reduced errors, and

increased productivity. This approach aligns with the core objectives of business analysis, which

include understanding and defining requirements, analyzing business processes, and recommending

solutions that deliver value to stakeholders. Simplification often involves removing unnecessary

steps, automating tasks, and optimizing workflows, which are key activities in business process

improvement. Reference: The BABOK® Guide outlines the importance of simplifying processes as

part of the requirements analysis and design definition. It emphasizes the role of the BA in

identifying areas where complexity can be reduced to improve business operations. Additionally, the

Business Analysis Learning documents highlight the significance of process simplification in achieving

operational excellence and delivering business value.

In business analysis, the predictive approach is characterized by its structured nature, where

requirements are approved at the end of a phase or during planned change control meetings. This

approach is in contrast to adaptive approaches, which approve requirements more iteratively and as

needed throughout the project lifecycle. Reference: The information is consistent with the practices

described in the BABOK Guide and other IIBA resources, which specify that predictive approaches

typically involve approvals at the end of the phase12.

A predictive planning approach (also known as waterfall or plan-driven) emphasizes upfront

planning, thorough documentation, and clearly defined stages of work. One of its key characteristics

is that information is captured in standardized templates, ensuring consistency, traceability, and

formal approvals at each stage.

Other characteristics include:

Sequential task execution

Emphasis on documentation and traceability

Clear role definitions and responsibilities

Reduced flexibility to accommodate change mid-project

This is different from adaptive or Agile approaches, which rely on iterations, minimal documentation,

and continuous stakeholder feedback.

BABOK® Reference:

Detailed in the Business Analysis Planning and Monitoring knowledge area under “Approaches and

Techniques,” where predictive approaches are contrasted with adaptive approaches based on their

structure, documentation, and flexibility.

Transition requirements are the only category of requirements that are temporary in nature. They

define the capabilities that a solution must have to facilitate the transition from the current state to

the future state, but they are not needed once the transition is complete. These include data

conversion, training, and deployment needs.

They support the implementation but are not part of the long-term functioning solution. This

distinguishes them from business, stakeholder, and solution requirements, which are ongoing or

permanent once implemented.

BABOK® Guide v3 – Section 2.3.4: Transition Requirements:

“Transition requirements describe the capabilities that the solution must have to facilitate transition

from the current state to the future state, but that will not be needed once that transition is

complete.”

User stories are a technique used in business analysis to represent a small, concise statement of

functionality or quality needed to deliver value to a specific stakeholder. They are expressed by

presenting the role, the goal, or the value and are a fundamental component of Agile methodologies.

User stories help teams understand what the stakeholders need without going into excessive detail,

allowing for iterative development and refinement of requirements.

Reference: The information is verified as per the Business Analysis Learning documents and

resources, which discuss various techniques including user stories as a way to capture stakeholder

needs and prioritize development of solutions12.

In the Elicitation and Collaboration knowledge area, the task "Prepare for Elicitation" takes "needs"

and "stakeholder engagement approach" as key inputs. The purpose of this task is to understand the

scope, identify stakeholders, choose elicitation techniques, and prepare the logistics to ensure a

productive elicitation session.

Needs define the business problem or opportunity prompting the elicitation.

Stakeholder engagement approach outlines how stakeholders will be involved, influencing

techniques and planning.

BABOK® Guide v3 – Section 4.1: Prepare for Elicitation:

Inputs: "Needs" and "Stakeholder Engagement Approach"

“The purpose of Prepare for Elicitation is to understand the scope of the elicitation activity, select

appropriate techniques, and plan for the elicitation.”

Thank you for your visit.

The core concept that defines a specific way of satisfying one or more needs in a context is

‘Solution’. According to the Business Analysis Core Concept Model™ (BACCM™), a solution satisfies a

need by resolving a problem faced by stakeholders or enabling stakeholders to take advantage of an

opportunity. It is a specific response to a need within a given context, and it can vary significantly

from one organization to another as different organizations or situations may require different

solutions.

Reference: This explanation is consistent with the definitions provided in the Business Analysis Core

Concept Model (BACCM™) as outlined by the International Institute of Business Analysis (IIBA) and

the Business Analysis Body of Knowledge (BABOK) guide1234.

Checklists are a tool used by business analysts for quality control when verifying requirements and

designs. They help ensure that all necessary steps are followed, and all important aspects are

considered. Checklists can capture any identified issues and are used to confirm that nothing crucial

is missed during the verification process. This tool is particularly useful for specifying and modeling

requirements, as it helps maintain the quality and completeness of the requirements

documentation. Reference: The use of checklists for quality control in business analysis is discussed

in the context of verification activities, which are essential throughout the project lifecycle to

maintain the validity of requirements and designs1.