2.1 Plan Business Analysis Approach
Key Takeaways
- The Business Analysis Approach defines the overall methodology, governing whether work is performed predictively (plan-driven) or adaptively (change-driven).
- Predictive approaches prioritize risk minimization, upfront formal documentation, and formal change control, making them suitable for high-compliance environments.
- Adaptive approaches emphasize rapid feedback, continuous stakeholder collaboration, and iterative refinement of user stories to maximize early value delivery.
- Key inputs into planning the approach include Business Needs, Organizational Capability, and Enterprise Architecture, resulting in the Business Analysis Approach output.
- Techniques such as Brainstorming, Business Cases, Process Modeling, and Risk Analysis help BAs tailor activity timing, formality, and deliverable detail.
2.1 Plan Business Analysis Approach
Overview & Purpose of BABOK Task 3.1
Planning the Business Analysis Approach is the foundational task in the Business Analysis Planning and Monitoring Knowledge Area, which is Chapter 3 of the BABOK Guide v3 (the tasks are therefore numbered 3.1 through 3.5). The primary purpose of Plan Business Analysis Approach is to define the overall method and set of processes for performing business analysis activities on a given initiative. It establishes how and when business analysis tasks will be executed, the level of formality and detail required for deliverables, and how activities will adapt as new information emerges.
Selecting an approach is not merely an administrative step; it directly influences stakeholder engagement, risk management, and the speed at which value is realized. A well-planned approach aligns business analysis activities with the broader organizational context, enterprise standards, and the specific characteristics of the solution being developed.
Predictive (Plan-Driven) vs. Adaptive (Change-Driven) Continuum
In BABOK® Guide v3, business analysis approaches exist along a continuous spectrum ranging from highly predictive (plan-driven, traditional Waterfall) to highly adaptive (change-driven, Agile/Scrum).
| Attribute | Predictive Approach (Plan-Driven) | Adaptive Approach (Change-Driven) |
|---|---|---|
| Primary Objective | Minimize uncertainty, control risk, and deliver scope as agreed upfront. | Deliver rapid value, accommodate emerging requirements, and incorporate frequent feedback. |
| Timing of BA Work | Requirements activities are concentrated upfront before design and execution. | Requirements activities are performed iteratively and continuously throughout the lifecycle. |
| Formality & Detail | High formality, standardized templates, formal sign-offs, exhaustive traceability. | Lower initial formality, user stories, acceptance criteria, just-in-time documentation. |
| Deliverables | Business Requirements Documents (BRD), Software Requirements Specs (SRS). | Product Backlog, User Stories, Epic maps, Working software increments. |
| Change Management | Formal Change Control Board (CCB), impact analysis, baseline modification. | Backlog refinement, sprint planning prioritization, flexible scope trade-offs. |
| Stakeholder Interaction | Structured formal reviews, milestone sign-offs, scheduled status reports. | Continuous daily collaboration, sprint reviews, hands-on user validation. |
| Suitable Environment | High regulatory compliance, fixed budgets, clear scope, heavy integration dependencies. | High market volatility, evolving business model, rapid time-to-market demands. |
Core Elements of the BA Approach
When planning the approach, the business analyst must analyze and document the six elements defined in BABOK Guide v3 section 3.1.4:
1. Planning Approach
The planning approach itself sits on the predictive-to-adaptive continuum described above. Predictive planning front-loads the plan and controls deviation; adaptive planning re-plans at each iteration boundary. Most real initiatives are hybrids, and the BA states explicitly where on the continuum the effort sits.
2. Formality and Level of Detail of Business Analysis Deliverables
Formality refers to the degree of structure, standardization, and documentation rigor required. High formality is essential when requirements will be transferred to external vendors, when strict regulatory compliance applies (e.g., FDA, SEC, GDPR), or when team members are geographically dispersed. Informal approaches rely on direct conversation, whiteboards, and lightweight user stories.
3. Business Analysis Activities
The BA breaks the business analysis work into discrete activities and deliverables, determines which tasks will actually be performed, and integrates them into the wider delivery plan. This is where the BA decides, for example, that a formal requirements architecture will be built but a separate business case will not.
4. Timing of Business Analysis Work
The timing of BA work determines whether tasks are executed in distinct, sequential phases or in continuous iterations. Predictive timing performs elicitation, analysis, and specification upfront. Adaptive timing executes analysis tasks incrementally prior to each iteration or sprint.
5. Complexity and Risk
The size and complexity of the change, and the overall risk the effort carries for the organization, shape the approach. BABOK Guide v3 groups the drivers into two lists: technical and organizational complexity (size of the change, number of business areas and systems affected, geographic and cultural spread, technological complexity) and human/process risk (experience of the business analyst, available domain knowledge, stakeholder attitudes toward the change, and the time stakeholders can realistically commit).
6. Acceptance
The business analysis approach is reviewed and agreed to by key stakeholders. In more structured organizations, key stakeholders formally sign off on the approach before business analysis work begins. Acceptance is what turns a BA’s private plan into a shared, governed commitment — and it is the element candidates most often forget to list.
Practitioner note: Deliverable formats and how the plan itself gets changed are handled inside the Business Analysis Activities and Planning Approach elements. In a predictive approach, deliverables are structured documents (Business Requirements Documents, System Architecture Specifications) and plan changes require formal baseline change requests. In an adaptive approach, deliverables are prioritized backlog items with a Definition of Done, and the plan is revised during retrospectives and iteration planning.
BACCM (Business Analysis Core Concept Model) Alignment
Applying the Business Analysis Core Concept Model (BACCM) ensures that the approach accounts for all core dimensions of business analysis:
| Core Concept | Application to Planning the BA Approach |
|---|---|
| Change | Define how the approach manages requirements changes—whether through formal change control or continuous backlog refinement. |
| Need | Determine how business needs will be uncovered and validated against the business case. |
| Solution | Tailor BA techniques based on whether the solution involves off-the-shelf software, custom development, or process re-engineering. |
| Stakeholder | Assess stakeholder availability, geographical location, and preferences to set communication cadence. |
| Value | Structure analysis activities to maximize early value delivery and reduce waste. |
| Context | Align the approach with enterprise architecture, regulatory environments, and organizational culture. |
Inputs, Guidelines, and Outputs
Understanding the precise inputs, guidelines, and outputs for Task 3.1 is critical for the CBAP exam:
-
Input (there is exactly one):
- Needs: The business problem or opportunity that drives the initiative. On the exam, resist answers that add enterprise architecture, organizational capability, or the business case to the input list for this task — BABOK Guide v3 lists Needs and nothing else.
-
Guidelines and Tools:
- Business Analysis Performance Assessment from previous initiatives (lessons learned).
- Business Policies that constrain how business analysis work may be performed.
- Expert Judgment on approach, methodology, and estimating.
- Methodologies and Frameworks already adopted by the enterprise (e.g., Scrum, SAFe, stage-gate waterfall).
- Stakeholder Engagement Approach, where one already exists from a prior effort.
-
Outputs:
- Business Analysis Approach: A comprehensive description of the selected approach, including BA task structures, deliverable formats, timing, and governance integration.
Key BABOK Techniques for Planning the Approach
- Brainstorming: Elicit ideas from team members regarding potential risks, delivery constraints, and analysis activities.
- Business Cases: Evaluate financial and strategic objectives to determine if a rapid adaptive deployment or a risk-mitigated predictive plan is needed.
- Process Modeling: Map current and future state processes to gauge the complexity of analysis work.
- Risk Analysis and Management: Identify potential risks (e.g., lack of stakeholder availability, strict regulatory deadlines) and build risk responses into the BA approach.
Enterprise Scenario: Selecting the BA Approach
Scenario: Financial Global Corp is replacing its legacy core accounting engine with a cloud-native platform while simultaneously launching a customer-facing mobile payment app.
Analysis & Application:
- For the core accounting engine, the BA selects a predictive approach due to high audit requirements, complex legacy data mappings, and zero tolerance for calculation errors. Deliverables include formal functional specifications and fully traced regulatory compliance matrices.
- For the mobile payment app, the BA selects an adaptive approach to enable weekly feature drops, rapid user feedback integration, and A/B testing. Elicitation occurs via user story workshops, and deliverables consist of prioritized backlog stories and interactive wireframes.
CBAP Exam Tips & Triggers
- Exam Trigger: If a question mentions "strict regulatory mandates", "external vendor contracting", or "fixed-price external bidding", select answers that favor a predictive (plan-driven) approach.
- Exam Trigger: If a question mentions "rapidly changing market conditions", "high solution volatility", or "frequent prototype feedback", choose answers aligned with an adaptive (change-driven) approach.
- Key Distinction: The Business Analysis Approach is created by the BA, but it MUST align with the overall project management approach and enterprise policies.
A senior business analyst is assigned to a high-risk enterprise initiative governed by stringent federal banking compliance regulations. The solution involves third-party system integration with heavy audit trail constraints. Which business analysis approach should the analyst select?
During the initial planning phase of a mobile e-commerce application, the business analyst observes that business rules and user expectations are rapidly evolving due to volatile market conditions. Which factor is the primary driver for selecting an adaptive BA approach?
When defining the element of 'Formality and Level of Detail' for business analysis deliverables in an agile software delivery project, which practice best reflects BABOK guidance?
A business analyst is evaluating potential risks related to stakeholder availability and technical complexity to establish the timing of business analysis work. Which BABOK technique is specifically designed to assess these factors during approach selection?