Business analysis planning and monitoring (BAPM) is the BABOK Guide v3 knowledge area where the business analyst decides how the analysis work will be done, who takes part, who decides, where information lives, and how the work is improved. It is chapter 3 of the BABOK Guide, has five tasks (3.1-3.5), and carries 14% of the Certified Business Analysis Professional (CBAP) exam, which is about 17 of 120 questions.
This article is the first in a ten-part series on BAPM. It gives the full map: purpose, weight, the five tasks with their inputs and outputs, how the outputs feed the other knowledge areas, a worked example, and what the exam checks. Later articles go deep into each task.
What business analysis planning and monitoring is and why it matters on the CBAP
BAPM is the set of tasks that organize and coordinate the work of business analysts and stakeholders, and its outputs guide every other task. The IIBA Business Analysis Standard describes BAPM this way and states that its outputs are used as guidance for the other tasks (IIBA KnowledgeHub).
BAPM is not project management. The project manager plans schedule, budget and staffing for the whole change. The business analyst plans the analysis work inside it: which activities, how formal, which stakeholders, which approvals. If you want to see where BAPM sits among the six knowledge areas, read the BABOK Guide as the backbone of business analysis.
CBAP exam facts
| Item | Value |
|---|---|
| Questions | 120 case-study and scenario-based multiple-choice |
| Time | 210 minutes, online proctored or at a PSI test centre |
| BAPM weight | 14% (about 17 questions) |
| Other weights | Elicitation and Collaboration 12%, Requirements Life Cycle Management 15%, Strategy Analysis 15%, Requirements Analysis and Design Definition 30%, Solution Evaluation 14% |
| Eligibility | 7,500 hours of BA work in the last 10 years, 35 professional development hours in the last 4 years, two references |
| Fees (USD) | Application $145; exam $505 ($350 members); rewrite $295 ($450 non-members) |
| Recertification | Every 3 years |
| Reference | BABOK Guide v3 |
Last verified: October 2026, on the IIBA CBAP page. The 17-question figure is 14% of 120, rounded.
The five BAPM tasks with inputs and outputs
BAPM has five tasks, and each one produces exactly one output that later tasks reuse. The table below lists them as they appear in BABOK v3 chapter 3. The inputs and outputs match the IIBA task cards for this knowledge area (IIBA task cards).
| Task | Purpose in one line | Inputs | Output |
|---|---|---|---|
| 3.1 Plan Business Analysis Approach | Choose the method for the BA work | Needs | Business analysis approach |
| 3.2 Plan Stakeholder Engagement | Plan how to work with stakeholders | Needs, business analysis approach | Stakeholder engagement approach |
| 3.3 Plan Business Analysis Governance | Define how decisions, changes and approvals happen | Business analysis approach, stakeholder engagement approach | Governance approach |
| 3.4 Plan Business Analysis Information Management | Define how BA information is stored, traced and accessed | Business analysis approach, governance approach, stakeholder engagement approach | Information management approach |
| 3.5 Identify Business Analysis Performance Improvements | Assess BA work and plan improvements | Business analysis approach, performance objectives (external) | Business analysis performance assessment |
Notice the chain. Task 3.1 has a single input, needs. Each later planning task takes the outputs of the tasks before it. Task 3.5 is the only one that adds an outside input: performance objectives set by the organization.
3.1 Plan Business Analysis Approach
Plan Business Analysis Approach is the task where you choose how the analysis will run. Its elements cover the planning approach (predictive, adaptive or a mix), the formality and level of detail of deliverables, the BA activities, their timing, complexity and risk, and acceptance of the approach by key stakeholders. An IIBA planning guide by Giorgos Sioutzos walks through the same steps and adds a practical rule: regulated or high-impact work, such as systems that handle money or health, usually needs a more controlled, predictive approach (IIBA, 9 steps to planning).
3.2 Plan Stakeholder Engagement
Plan Stakeholder Engagement is the task where you identify stakeholders, analyse them, and decide how you will collaborate and communicate with each group. The elements are stakeholder analysis, stakeholder collaboration, and stakeholder communication needs (BusinessAnalystMentor). The techniques most tied to it are covered in stakeholders and personas.
3.3 Plan Business Analysis Governance
Plan Business Analysis Governance is the task where you define who makes decisions about requirements and designs, how changes are controlled, how priorities are set, and who approves what. Its four elements are decision making, change control process, prioritization approach, and approvals. The business analyst facilitates these processes; the named decision maker decides.
3.4 Plan Business Analysis Information Management
Plan Business Analysis Information Management is the task where you decide how analysis information is organized, at what level of abstraction, how it is traced, reused, stored and accessed, and which attributes each requirement carries. This plan is what later makes traceability of requirements possible instead of a last-minute spreadsheet.
3.5 Identify Business Analysis Performance Improvements
Identify Business Analysis Performance Improvements is the task where you measure how well the BA work is going and recommend changes. Its elements are performance analysis, assessment measures, analysing results, and recommending actions. The IIBA task card lists lessons learned, metrics and KPIs, process analysis, process modelling and root cause analysis among its techniques. This is the monitoring half of the knowledge area name.
How BAPM outputs feed the other knowledge areas
BAPM outputs are reused across the whole BABOK, either as inputs or as guidelines and tools for later tasks. The table shows the most testable links, each checked against public IIBA material or a second study source.
| BAPM output | Where it shows up later | Why it matters |
|---|---|---|
| Business analysis approach | Inputs of 3.2-3.5; guidance for elicitation and other tasks | Sets how formal and how iterative all later work is |
| Stakeholder engagement approach | Used in 4.1 Prepare for Elicitation; input to 4.5 Manage Stakeholder Collaboration | Tells you who to involve and how |
| Governance approach | Guideline for 5.3 Prioritize Requirements; guides approvals in 5.5 | Defines who decides on priority, change and sign-off |
| Information management approach | Guides tracing, maintenance and reuse in Requirements Life Cycle Management | Defines storage, attributes and traceability |
| Business analysis performance assessment | Input to 4.5 Manage Stakeholder Collaboration; guideline for planning tasks 3.1-3.4 | Closes the loop: lessons feed the next plan |
Sources: the IIBA Elicitation and Collaboration task cards, the Open Exam Prep summary of task 4.5, and the IIBA task card for Prioritize Requirements. For the downstream areas themselves, see elicitation and collaboration and requirements life cycle management.
A useful way to remember it: BAPM answers five questions once, and the rest of the BABOK keeps asking them. How do we work? With whom? Who decides? Where does it live? Is it working?
Worked example: planning BA work on a checkout project
A worked example shows that the five tasks are short decisions made in order, not five documents. The scenario below is invented for this article.
Context. A mid-size online retailer wants to replace its payment provider and redesign the checkout page. The sponsor's need: cut payment failures and lower card fees. You are the lead business analyst and join in week one.
3.1 Business analysis approach. The payment integration has security and card-scheme rules, so you plan that part predictively: formal requirements, reviewed and signed before build. The checkout user interface is uncertain, so you plan it adaptively: two-week iterations, prototypes, and acceptance criteria per user story. You list activities (document analysis of current failure logs, interviews with finance, prototype tests with customers), set their timing against release milestones, and note complexity and risk: an external vendor, a fixed contract date, and compliance review. The sponsor and the product owner agree to this approach in a 30-minute meeting.
3.2 Stakeholder engagement approach. You list stakeholders: sponsor (commercial director), product owner, payments developers, finance, legal and compliance, customer support, the payment vendor, and customers. Finance has high influence and low interest in the interface; customer support has low influence but sees every failed payment. You plan a weekly demo for the product owner and developers, a monthly written update for finance, and two support-agent interviews per iteration.
3.3 Governance approach. The product owner decides priority for checkout user stories. Any change to payment or security requirements after sign-off goes to a small change board: product owner, security lead and finance. You prepare impact analysis; the board decides. Compliance signs off the security requirements before go-live.
3.4 Information management approach. Requirements and user stories live in the team's backlog tool, and payment rules live on one wiki page per rule. Each payment requirement carries attributes for source, priority, status and owner, and traces to the compliance control it supports. Interface stories trace only to the business objective, because heavy tracing there would cost more than it saves.
3.5 Performance assessment. The sponsor sets an objective: no more than 10% of stories returned from sprint review for unclear acceptance criteria. After three iterations the rate is 25%. A short root cause session shows that customer support never reviewed the criteria. You add support to backlog refinement, update the stakeholder engagement approach, and the rate falls in the next two iterations.
The loop is the point. Task 3.5 changed the output of task 3.2, which is exactly how the BABOK expects BAPM to work.
What practitioners and candidates say
Practitioners agree that the approach must be built for each context, and candidates agree that the exam rewards BABOK reasoning over workplace habit.
- Laura Brandenburg of Bridging the Gap argues that the BABOK is not a methodology, so the analyst must build one. She writes that "planning the business analysis approach will set a mature business analyst apart" (Bridging the Gap, 2011). On a large consolidation with several BAs, her team needed shared templates, agreed detail levels and a prioritization method.
- In a 2022 article she advises deferring a BA estimate until you understand scope and your role, after meeting the main business stakeholder and the lead developer (Bridging the Gap, 2022). That is task 3.1 and 3.2 in practice.
- Trainer Shrushti Gupta warns that "practical experience alone does not make someone exam-ready" and suggests studying each task by why, inputs, participants, techniques and result (Modern Analyst, 2026).
- Elizabeth Larson summarized recent CBAP holders on BABOK v3: most studied 150-200 hours, reviewed inputs, outputs and stakeholders for every task, and learned task sequence for "what next" questions (BA Times).
- Candidate Rami Kaibni reported that removing two options is usually easy, but choosing between the last two needs close reading (ProjectManagement.com, 2019).
- Candidate Satheesh S, who prepared in about 90 hours, recommends memorizing some inputs and outputs but linking them to real projects so they stick (Techcanvass, 2024).
What the CBAP exam looks for in BAPM
The CBAP exam tests BAPM through scenarios that ask what the analyst should plan, use or do next, not through definitions. Based on the official sample question and the candidate reports above, expect these patterns.
- Sequence. Planning comes before elicitation. If a scenario has no agreed approach yet, the best answer is usually to plan, not to start interviews.
- Inputs versus outputs. The only input to 3.1 is needs. A trap answer offers an output as an input. Adaptive US notes that confusing inputs and outputs is a common distractor (Adaptive US).
- Inputs versus guidelines. The business analysis performance assessment guides 3.1-3.4 but is not their formal input.
- Who decides. The analyst facilitates governance; the decision maker decides. Answers where the BA approves a change alone are usually wrong.
- Formality follows risk. Regulated, high-impact work calls for more formal deliverables, whatever the team prefers.
- Adaptive still plans. An adaptive approach plans in short cycles; it does not skip planning.
- Stakeholder attitude is a risk. In the official IIBA sample, a long-tenured vice president disagrees with the project's objectives, and the keyed answer is risk analysis and management, not a new engagement plan.
A later article in this series covers the most common BAPM exam traps in detail. To practise the same scenario style on another IIBA credential, try the IIBA CBDA practice exam.
Practice Questions
These four original questions follow the CBAP scenario style. Answers and explanations follow each one.
Question 1
A business analyst is asked to start work on a new initiative. No method for the analysis work has been agreed. Which item is the input the analyst needs to plan the business analysis approach?
A. Stakeholder engagement approach B. Needs C. Business analysis performance assessment D. Governance approach
Answer: B. Task 3.1 Plan Business Analysis Approach has one input: needs (BABOK v3, 3.1). A and D are outputs of later tasks 3.2 and 3.3. C is a guideline and tool from earlier work, not an input.
Question 2
Mid-project, stakeholders email new requirements straight to developers after sign-off. Nobody knows who can accept or reject them. Which planning output is missing or weak?
A. Information management approach B. Stakeholder engagement approach C. Governance approach D. Business analysis approach
Answer: C. The governance approach defines decision making, change control, prioritization and approvals (BABOK v3, 3.3). A clear change control process would route new requests to a named decision maker. B may also need attention, but the root problem is undefined decision rights.
Question 3
An auditor asks a team to show which requirements support a new regulation, where they are stored and who changed them last. The team needs two days to find the answer. Which task should the analyst revisit first?
A. Plan Business Analysis Information Management B. Plan Stakeholder Engagement C. Identify Business Analysis Performance Improvements D. Plan Business Analysis Approach
Answer: A. Traceability approach, storage and access, and requirements attributes are elements of task 3.4 (BABOK v3, 3.4). C would help find the cause, but the fix lives in the information management approach.
Question 4
The sponsor expects requirement reviews to close in one round. On the last three features they took three rounds each. What should the business analyst do first?
A. Replace the review technique with a workshop for all future features B. Analyse the results against the objective and find the cause of the extra rounds C. Ask the sponsor to lower the objective D. Add more reviewers so that issues are found earlier
Answer: B. Task 3.5 asks the analyst to analyse results against assessment measures before recommending actions (BABOK v3, 3.5). A and D jump to solutions without evidence. C ignores the external performance objective, which is an input to this task.
Key takeaways
- BAPM is 14% of the CBAP exam, about 17 of 120 questions (IIBA, October 2026).
- Five tasks, five outputs: business analysis approach, stakeholder engagement approach, governance approach, information management approach, business analysis performance assessment.
- Task 3.1 has one input, needs; each later planning task builds on the earlier outputs.
- BAPM outputs guide elicitation, stakeholder collaboration, prioritization, approval and traceability.
- The analyst plans and facilitates; named stakeholders decide and approve.
- Formality follows risk and context, and adaptive work still plans.
- For the techniques you will meet in each area, use the BABOK techniques map by knowledge area.
FAQ
How many CBAP questions come from business analysis planning and monitoring?
BAPM carries 14% of the CBAP exam according to the IIBA blueprint (checked October 2026). With 120 questions, that is about 17 questions. Expect them as scenarios rather than definitions.
What are the five tasks of BAPM in BABOK v3?
The tasks are 3.1 Plan Business Analysis Approach, 3.2 Plan Stakeholder Engagement, 3.3 Plan Business Analysis Governance, 3.4 Plan Business Analysis Information Management, and 3.5 Identify Business Analysis Performance Improvements. Each task produces one output that other tasks reuse.
Is the business analysis approach the same as the project plan?
No. The project plan covers schedule, budget and resources for the whole change. The business analysis approach covers only how the analysis work is done: method, formality, activities, timing, risk and stakeholder acceptance. On the exam, an answer that treats them as one document is usually a distractor.
Do agile teams need BAPM?
Yes. BABOK v3 treats predictive and adaptive approaches as two ends of one scale, and both need a plan. In adaptive work the planning is lighter and repeats every iteration, but stakeholders, decision rights and information storage still have to be agreed.
Should I memorize all BAPM inputs and outputs?
Memorize the five outputs and the input chain, because exam distractors often swap an input with an output. Candidates who passed also recommend linking each task to a real project so you can answer scenario questions about what to do next.
Sources
- IIBA: CBAP certification page
- IIBA KnowledgeHub: Business Analysis Planning and Monitoring
- IIBA: BAPM task cards (PDF)
- IIBA: Prioritize Requirements task card (PDF)
- IIBA: 9 steps to planning, Giorgos Sioutzos (PDF)
- BusinessAnalystMentor: Business Analysis Planning and Monitoring
- Open Exam Prep: Manage Stakeholder Collaboration (Task 4.5)
- Bridging the Gap: The BABOK might not be a methodology, but the BA still needs one
- Bridging the Gap: How to create a business analyst timeline
- Modern Analyst: How business analysts can prepare for the CBAP exam
- BA Times: How to pass the CBAP exam, study tips from recent credential holders
- ProjectManagement.com: Certified Business Analysis Professional (CBAP), Rami Kaibni
- Techcanvass: How I aced the CBAP exam
- Adaptive US: CCBA and CBAP scenario-based questions