What Is Business Analysis?
Key Takeaways
- BABOK Guide v3 defines business analysis as "the practice of enabling change in an enterprise by defining needs and recommending solutions that deliver value to stakeholders."
- Business analysis can be performed within a chartered project or independent of one, such as during strategy analysis or ongoing operational improvement.
- BABOK Guide v3 identifies five perspectives — Agile, Business Intelligence, Information Technology, Business Architecture, and Business Process Management — that shape how BA techniques are emphasized.
- Business analysis is defined by the work performed, not by job title; business analysts, product owners, business architects, and consultants all perform business analysis when they define needs and recommend solutions.
- Because business analysis enables change generally rather than a specific technology, it applies across every industry, from healthcare and government to retail and manufacturing.
Defining Business Analysis
The BABOK Guide v3 defines business analysis as "the practice of enabling change in an enterprise by defining needs and recommending solutions that deliver value to stakeholders." Two phrases in that definition drive most of what the ECBA exam tests. First, business analysis enables change — a business analyst does not personally own, fund, or execute the change; the analyst produces the understanding that lets sponsors and delivery teams make good decisions about it. Second, the work is anchored to value: every need identified and every solution recommended exists to deliver worth to the stakeholders who will live with the outcome, not simply to produce a document or a system.
Business analysis is broader than "writing requirements." It spans identifying problems and opportunities, understanding what different stakeholders actually need, evaluating solution options against that need, and confirming afterward that the promised value actually materialized. A practitioner who only gathers requirements without tracing them back to a validated need and an expected value outcome has done part of the job, not the whole job.
Where Business Analysis Happens
Business analysis is not confined to chartered projects. The Business Analysis Standard recognizes that BA work happens in several settings:
- Within a project or initiative — once an effort has a defined scope, timeline, and budget, business analysis supports requirements definition, design input, and solution evaluation for that specific change.
- Independent of a project — strategy analysis, enterprise-level opportunity assessment, and continuous improvement of ongoing operations are business analysis even though no project has been chartered yet. A BA scanning a competitive landscape to identify a strategic gap is doing business analysis before any initiative exists.
- At the operational or solution level — after a solution is live, analyzing how well it performs against the original need is still business analysis, not a separate discipline.
This distinction matters for the exam because situational questions often test whether a candidate can recognize business analysis work in a non-project setting — for example, a BA asked to investigate a recurring customer-complaint pattern with no project yet defined is still performing legitimate business analysis.
Who Performs Business Analysis
Business analysis is defined by the work performed, not by the title on someone's badge. People who regularly perform business analysis tasks include business analysts, business systems analysts, systems analysts, product owners, business architects, management consultants, and even project managers or subject matter experts when they take on BA-type activities such as defining needs or evaluating solution options. The Business Analysis Standard is explicit that the discipline is role-agnostic: if the tasks being performed match business analysis — defining needs, recommending solutions, assessing value — the work counts as business analysis regardless of the practitioner's formal title.
The Five BABOK Perspectives
The BABOK Guide v3 introduces five perspectives that describe how business analysis emphasis shifts depending on the type of initiative:
| Perspective | Primary Focus |
|---|---|
| Agile | Iterative, incremental delivery; adaptive planning; continuous, close collaboration with a delivery team |
| Business Intelligence | Analyzing data and building reporting/analytics capability to support decision-making |
| Information Technology | Eliciting, analyzing, and managing requirements for IT-enabled solution delivery |
| Business Architecture | Aligning enterprise strategy, capabilities, and organizational structure |
| Business Process Management | Analyzing, redesigning, and continuously improving business processes |
A perspective is a lens, not a separate methodology. The same underlying BA work — elicitation, analysis, solution evaluation — is performed regardless of perspective, but the emphasis and vocabulary shift. A BA working on a data warehouse initiative leans on the Business Intelligence perspective; a BA embedded with a Scrum team leans on Agile; a BA supporting an operating-model redesign leans on Business Architecture.
Enabling Change Across Contexts
Because business analysis enables change rather than a specific technology, it applies across virtually every industry and change type: a hospital redesigning patient intake, a bank responding to new regulatory requirements, a government agency digitizing a permitting process, a retailer replacing a point-of-sale platform, or a manufacturer re-engineering a supply-chain workflow. In every case the underlying BA work is the same — understand the need, engage the right stakeholders, evaluate solution options within the organization's context, and confirm the change delivers value.
This context-independence is why the ECBA blueprint treats "Understanding Business Analysis" as the foundational domain, carrying the largest single weight of any domain on the exam. Every other domain — Change, Need, Solution, Stakeholder, Value, and Context — is an application of this core discipline to a specific concern. Recognizing business analysis work when it appears in an unfamiliar industry, an unfamiliar methodology, or under an unfamiliar job title is a recurring situational-question pattern on the ECBA exam, and it starts with internalizing this baseline definition.
A consultant is asked to identify strategic problems and opportunities at the enterprise level, months before any project has been chartered or funded. Which statement best describes this work?
A product owner, a business architect, and a management consultant are each defining needs and recommending solutions on their respective initiatives, though none of them has the job title "Business Analyst." Which of the following best reflects who performs business analysis according to the Business Analysis Standard?