The predictive vs adaptive choice is the first decision in Business Analysis Planning and Monitoring (BAPM), and it shapes all five BAPM tasks in BABOK Guide v3. A predictive approach defines the solution before building it and controls change against a baseline. An adaptive approach delivers in short iterations and accepts more uncertainty. BAPM is 14% of the Certified Business Analysis Professional (CBAP) exam, and many of its scenarios hinge on this choice.
Last verified: October 2026 (exam facts from iiba.org).
What predictive vs adaptive means in BABOK
A predictive approach is a plan-first way of working: business analysis effort is concentrated early, deliverables are formal, and changes go through a defined control process. An adaptive approach is an iterate-first way of working: analysis runs continuously, deliverables are as light as the team can afford, and feedback from each increment drives the next plan.
BABOK v3 introduces the choice in task 3.1 Plan Business Analysis Approach, under the planning approach element. In practice the two work as ends of a range, not as two boxes, and many initiatives sit somewhere between them.
IIBA's current KnowledgeHub material says the same. It describes predictive work as planning the full scope up front and adaptive work as delivering value in small, prioritized increments. It also names hybrid as a third option, either across initiatives or inside one initiative (IIBA, Approaches to Your Work).
| Factor | Points to predictive | Points to adaptive |
|---|---|---|
| Need and solution | Well understood, stable | Unclear, likely to emerge |
| Regulation and audit | Heavy, formal evidence required | Light, or evidence can be produced per release |
| Cost of a late change | High (hardware, contracts, integrations) | Low (software that can be released often) |
| Stakeholder availability | Limited, available at milestones | Available often, can review each increment |
| Risk tolerance | Low; uncertainty must be removed up front | Higher; uncertainty is reduced by delivering |
Why the exam cares about this choice
The approach is the first output of BAPM, and every later BAPM task takes it as an input. Task 3.2 uses the business analysis approach. Task 3.3 uses it plus the stakeholder engagement approach. Task 3.4 uses the approach, the stakeholder engagement approach and the governance approach. Task 3.5 uses the approach and performance objectives (IIBA BAPM task cards).
So if a scenario quietly tells you the team works in two-week iterations, that fact should change your answer about approvals, traceability and lessons learned too. The approach is the root of the BAPM input chain, so a wrong reading of it spreads to every later answer.
CBAP facts you need for context:
| Item | Value |
|---|---|
| Questions | 120 case-study and scenario-based multiple-choice |
| Time | 210 minutes |
| BAPM weight | 14% |
| Eligibility | 7,500 hours of BA work in the last 10 years; 35 PD hours in the last 4 years; two references |
| Fees (USD) | Application $145; exam $505 (members $350) |
| Reference | BABOK Guide v3 |
Source: IIBA CBAP page. Last verified: October 2026.
Predictive vs adaptive in each BAPM task
Each task below gets one comparison table. The rows paraphrase how BABOK v3 and IIBA describe each approach; they are tendencies, not rules.
3.1 Plan Business Analysis Approach
The approach task sets the planning approach, the formality and level of detail of deliverables, the timing of activities, complexity and risk, and how the approach itself is accepted. Deeper coverage is in Plan Business Analysis Approach.
| Aspect | Predictive | Adaptive |
|---|---|---|
| Planning | Most planning done before build starts | Short-term plans, repeated each iteration |
| Formality | Formal documents, standard templates, sign-off | Lighter artifacts; shared understanding through conversation and feedback |
| Timing | BA effort heavy at the start or in early phases | BA effort spread across the whole initiative |
| Risk handling | Reduce uncertainty before committing | Accept uncertainty, reduce it by delivering increments |
| Acceptance of the approach | Agreed once with key stakeholders, revised by change | Agreed, then revisited as the team learns |
IIBA's task card stresses that this planning is "equally important for an adaptive approach" (IIBA task cards). Adaptive teams still plan; they plan in smaller pieces.
3.2 Plan Stakeholder Engagement
The engagement task covers stakeholder analysis, how stakeholders will collaborate, and what they need to hear and when. See Plan Stakeholder Engagement for the full task.
| Aspect | Predictive | Adaptive |
|---|---|---|
| Stakeholder analysis | Done thoroughly early, refreshed at phase gates | Done early, refreshed often as new stakeholders appear |
| Collaboration | Planned events: workshops, reviews, sign-off meetings | Continuous: refinement sessions, demos, daily contact |
| Communication | Scheduled status reports and formal documents | Frequent, informal, face to face where possible |
| Key risk | Stakeholders disengage between milestones | Stakeholders cannot keep up with the cadence |
3.3 Plan Business Analysis Governance
Governance defines who decides, how change is controlled, how work is prioritized and how approvals happen. More detail is in business analysis governance.
| Aspect | Predictive | Adaptive |
|---|---|---|
| Decision making | Defined roles and escalation paths, often a steering group | Product owner or equivalent decides day to day |
| Change control | Formal change requests, impact analysis, change board, new baseline | Change is expected; handled by reprioritizing the backlog |
| Prioritization | Set early to fix the scope of a phase | Continuous, per iteration, by value |
| Approvals | Formal sign-off on a requirements package at phase end | Frequent, small approvals, such as acceptance of items at a review |
Change control does not disappear in adaptive work. Contract, budget or regulatory changes may still need a formal path even when backlog changes do not.
3.4 Plan Business Analysis Information Management
Information management decides how information is organized, at what level of abstraction, how it is traced, reused, stored and described with attributes. The full task is in business analysis information management.
| Aspect | Predictive | Adaptive |
|---|---|---|
| Organization | Document sets per phase, often a requirements specification | Backlog items, story maps, living models |
| Level of abstraction | Detailed before build | Coarse items, detailed just before they are built |
| Traceability | Full, bidirectional, often audited | Lighter; enough to manage dependencies and value |
| Storage and access | Controlled repository with versioned baselines | Shared tool the whole team updates daily |
| Attributes | Many (source, status, owner, stability, version) | Few, kept only if someone uses them |
3.5 Identify Business Analysis Performance Improvements
The performance task measures how well BA work is going and recommends improvements. See business analysis performance improvements.
| Aspect | Predictive | Adaptive |
|---|---|---|
| When assessed | Milestones, phase ends, project close | Every iteration |
| Typical event | Lessons learned session | Retrospective |
| Measures | Variance against plan: schedule, effort, rework, defects | Flow and value: items accepted, rework per iteration, feedback quality |
| Speed of correction | Slow; improvements often reach the next project | Fast; improvements apply to the next iteration |
IIBA's task card calls continuous process improvement a mainstay of adaptive approaches, and says it matters just as much in predictive and hybrid ones (IIBA task cards).
Hybrid approaches: how they work in practice
A hybrid approach is a deliberate mix of predictive and adaptive practices, chosen part by part. It is the most common real setup, and it is where BAPM planning matters most.
Adriana Beal on Modern Analyst describes three kinds of hybrid project (Modern Analyst):
| Type | What it is | BA consequence |
|---|---|---|
| Frankenstein | "Agile" label, but full upfront sign-off and fixed scope remain | Conflicting expectations; change from feedback gets resisted |
| Cross breed | Practices combined on purpose, each kept only if it adds value | Progressive elaboration plus traditional models where useful |
| Combo | Plan-driven for stable, critical components; agile for volatile ones | Formal early documentation for some parts, just-in-time for others |
Lavinia Mihaela Dinca, writing on BA Times, lists the practical pains of a hybrid project: deciding the split, integrating priorities across both streams, documenting at two levels of detail, tracing requirements across both, and explaining to the team why each part uses its method (BA Times). Her fix for traceability is one common requirements matrix.
A useful planning rule follows from both articles. In a hybrid setup, plan each BAPM output per part of the solution. A regulated core might get a formal change board and full traceability, while the customer-facing front end runs on backlog reprioritization and retrospectives. Write both down in the business analysis approach so nobody has to guess.
The IIBA Agile Extension adds another angle: it describes planning at three horizons (Strategy, Initiative and Delivery), each with its own planning depth and feedback cycle. Our article on Agile Extension horizons explains how the horizons relate.
How CBAP scenarios signal the approach
CBAP questions rarely say "this is a predictive project." They leave cues. Read the stem for them before reading the options.
| Cue in the scenario | Likely approach | What changes in the best answer |
|---|---|---|
| Baseline, sign-off, change control board, phase gate, requirements specification | Predictive | Formal change requests, impact analysis, approval at defined points |
| Sprint, iteration, backlog, product owner, demo, retrospective | Adaptive | Reprioritize, refine just in time, improve at the next retrospective |
| Regulator, audit, fixed-price contract, safety-critical | Predictive or hybrid | More formality, fuller traceability, documented approvals |
| Unclear need, new market, "the sponsor will know it when they see it" | Adaptive | Prototype, iterate, short feedback loops |
| Some components stable, others volatile | Hybrid | Different BAPM choices per component |
Techcanvass advises candidates to answer case-study questions from BABOK concepts rather than personal habit (Techcanvass). That matters here, because many candidates work in one approach and project it onto every scenario.
What practitioners report
Practitioner accounts agree that the BA role changes shape between approaches, not that it shrinks.
- Cecil Goldstein (Axis Agile, 2020) contrasts the waterfall BA, who gathers requirements up front and hands documents downstream, with the agile BA, who stays in the team for the whole initiative and uses rolling-wave analysis. He cites George Dinwiddie: "it's not the documentation that needs to be in sync, but the people" (Axis Agile).
- Gene Gendel (InfoQ, 2016), an agile coach, describes teams that receive a monolithic business requirements document inside sprints. They struggle to slice it, and status reporting drifts away from real progress (InfoQ). This is Beal's "Frankenstein" in daily life.
- Enterprise Knowledge presenters Yanko Ivanov and Tatiana Baquero Cakici, after moving a team from waterfall to agile, describe "a mental shift" for BAs in how they work with stakeholders and the team (Enterprise Knowledge).
- Joy Beatty, explaining the tailoring tables in PMI's business analysis standard, calls them "not a rule or policy, but rather a guideline" (ProjectManagement.com). Reviewers asked for this because predictive ideas often help adaptive teams, and the reverse.
- Tejaswinee Barua (BA Times, 2018) argues that BAs meet Agile, PRINCE2, waterfall and hybrid models in the same career, so adaptability is a core trait (BA Times).
The pattern across these sources: the method label matters less than whether the BAPM outputs match how the team really works.
Common misconceptions
"Adaptive means no planning." False. BAPM tasks apply to adaptive work too; planning happens in smaller, repeated steps.
"Adaptive means no documentation." False. Documentation is sized to need. Goldstein notes it is not eliminated; it serves value delivery instead of being the goal.
"Predictive means no change." False. Predictive approaches expect change and route it through a defined control process.
"Hybrid means doing both fully." False. A good hybrid picks one practice per part of the work. Doing both in full is Beal's Frankenstein.
"The BA picks the approach alone." False. The business analysis approach is agreed with key stakeholders, and the organization may already mandate a method. IIBA notes that an approach is sometimes imposed on the team.
"Retrospectives are only for adaptive teams." False. Performance improvement is required in every approach; predictive teams use lessons learned and variance analysis.
Practice Questions
These are original questions in the CBAP style. Answers follow each question.
Question 1. A business analyst joins an initiative that will replace the claims engine of an insurer. The regulator must approve the calculation rules before go-live. The customer portal on top of the engine will be redesigned using two-week sprints. What should the BA do when planning the business analysis approach?
- A. Use an adaptive approach for everything, since sprints are already planned.
- B. Use a predictive approach for everything, since a regulator is involved.
- C. Define a hybrid approach with formal approvals and traceability for the calculation rules and iterative elaboration for the portal.
- D. Postpone the choice until the first sprint review.
Answer: C. The scenario contains both a regulated, stable component and a volatile, iterative one. BABOK task 3.1 lets the BA tailor the approach, and a hybrid split matches the cues. A and B ignore half the scenario; D leaves the work unplanned.
Question 2. On an adaptive initiative, the sponsor asks for a new reporting feature halfway through the release. What is the BA's best first action?
- A. Raise a formal change request to the change control board.
- B. Work with the product owner to add the item to the backlog and prioritize it against existing items.
- C. Reject the request because the release scope is baselined.
- D. Update the signed requirements specification and ask for re-approval.
Answer: B. In an adaptive governance approach, change is absorbed through backlog prioritization by the agreed decision maker. A, C and D are predictive mechanisms that do not fit the cues "adaptive" and "backlog."
Question 3. A predictive project finished its design phase three weeks late. Reviews show many requirements were rewritten after sign-off. Which action best fits task 3.5?
- A. Wait for the project-close lessons learned session.
- B. Hold a retrospective after every sprint.
- C. Analyze the variance and its root cause now, and recommend changes to elicitation and review before the next phase.
- D. Remove the sign-off step to save time.
Answer: C. Performance improvement in a predictive project uses measures against the plan at milestones. The phase end is a valid point to analyze results and recommend actions. A delays correction, B assumes sprints that do not exist, and D removes a control without analysis.
For more timed practice in IIBA question style, try the IIBA CBDA practice exam; the scenario format is close to CBAP.
Related techniques
- Backlog management, estimation, item tracking and lessons learned are techniques whose use shifts noticeably between approaches: the same technique runs once per phase in predictive work and once per iteration in adaptive work.
- The Agile Extension horizons article shows how planning depth changes from strategy to delivery.
- Each BAPM task has its own deep dive, linked in the task sections above.
FAQ
What is the difference between predictive and adaptive approaches in BABOK?
A predictive approach defines most of the solution before building it and controls change against a baseline. An adaptive approach plans in short cycles, delivers increments, and accepts more uncertainty in return for faster feedback. IIBA also recognizes hybrid approaches that mix the two within or across initiatives.
Do BAPM tasks still apply on agile projects?
Yes. All five BAPM tasks apply to adaptive work. The outputs are lighter and revisited more often, but the BA still needs an approach, an engagement plan, governance, information management and performance assessment.
How do I tell which approach a CBAP question assumes?
Look for cue words in the stem. Baseline, sign-off, change control board and phase gate point to predictive. Sprint, backlog, product owner and retrospective point to adaptive. A mix of stable regulated parts and volatile parts points to hybrid.
Is hybrid a valid answer on the CBAP exam?
Yes, when the scenario supports it. BABOK v3 allows the BA to tailor the approach, and IIBA describes hybrid as a mix within or across initiatives. Pick hybrid only when the scenario contains both kinds of cues.
Does an adaptive approach remove change control?
No. Most change is handled by reprioritizing the backlog, but changes to budget, contracts or regulated content may still need formal approval. The governance approach should state which path each kind of change takes.
Sources
- IIBA, CBAP certification page (exam facts, verified October 2026)
- IIBA KnowledgeHub, Approaches to Your Work
- IIBA, BAPM task cards (PDF)
- Adriana Beal, The 3 types of hybrid projects, Modern Analyst
- Lavinia Mihaela Dinca, 5 Challenges for the Business Analyst on a Hybrid Project, BA Times (2016)
- Tejaswinee Barua, The Hybrid Business Analyst, BA Times (2018)
- Cecil Goldstein, How does the BA role change on an agile project, Axis Agile (2020)
- Gene Gendel, Waterfall requirements in agile, InfoQ (2016)
- Enterprise Knowledge, The Business Analyst Role: Agile v. Waterfall (2018)
- Joy Beatty, Adapting BA Processes for Adaptive vs Predictive Life Cycles, ProjectManagement.com (2017)
- Techcanvass, Tips for Solving CBAP Case Study Based Questions (2024)