Start free PMI-PBA practice and preview the simulator before purchase

A situation statement should describe the problem, its effects, and the resulting business impact without proposing a solution. Introducing a solution too early prevents proper assessment of the current state and identification of root causes before evaluating options.

Benchmarking involves comparing practices and performance with external organizations that have addressed similar challenges. This technique supports identification of future-state capabilities beyond the organization’s current environment.

Needs assessment focuses on understanding the problem or opportunity before evaluating solutions. Assessing a specific solution through external benchmarks represents prematurely jumping to a solution without clarifying the business need or root causes.

Enterprise environmental factors include external or internal conditions such as industry data, benchmarking results, and risk studies that influence business analysis work but are outside the control of the project team. These are not organizational assets or defined tasks.

Requirements represent needs, expectations, or requests from any stakeholder that are intended to solve problems or enable opportunities. They are not limited to customers, specific categories, or tangible products only.

By comparing the current state with competitors, the analyst identifies gaps in offered services. Performing gap analysis helps determine enhancements that can improve competitiveness and customer experience.

Business architecture techniques model business functions, structures, and processes, enabling analysis of strategic and operational impacts of change. This makes them suitable tools for advising leadership on strategic direction.

Feature injection focuses analysis and discussion on identifying features that provide immediate return on value. It helps stakeholders prioritize high-impact features early rather than analyzing all information equally.

Understanding stakeholders is essential because their needs, attitudes, behaviors, and expectations directly shape meaningful and usable requirements.

When a problem is identified, the business analyst should begin by performing a needs assessment to clearly define the issue, assess the current state, and understand root causes before proposing or evaluating solutions.