Plan Stakeholder Engagement (BABOK 3.2): A CBAP Deep Dive

Plan Stakeholder Engagement is BABOK Guide v3 task 3.2: the business analyst decides how to build and keep working relationships with stakeholders. You plan stakeholder engagement in three steps: analyse stakeholders (roles, attitudes, decision-making authority, power or influence), define how you will collaborate with them, and set their communication needs. The output is the stakeholder engagement approach. On the CBAP exam it sits in Business Analysis Planning and Monitoring, which is 14% of 120 questions.

Last verified: October 2026 (exam facts from the IIBA CBAP page).

What Plan Stakeholder Engagement is

Plan Stakeholder Engagement is the planning task that turns a list of people into a deliberate way of working with each of them. It is the second of five tasks in the Business Analysis Planning and Monitoring (BAPM) knowledge area, after Plan Business Analysis Approach (3.1). The series overview of BAPM shows how the five tasks connect.

The task card published by IIBA lists the parts below. The technique list comes from BABOK v3 and matches independent study summaries (IIBA task card; Viblo BABOK summary).

This post focuses on the task itself. For the difference between real stakeholders and user personas, read the older post on stakeholders and personas; it answers a different question.

Why plan stakeholder engagement matters on the CBAP exam

The exam tests whether you plan engagement before you start eliciting, and whether you adjust the plan when stakeholders change. The CBAP (Certified Business Analysis Professional) exam has 120 scenario-based questions in 210 minutes, and BAPM carries 14% of the blueprint, so expect roughly 17 BAPM questions (IIBA).

The stakeholder engagement approach also feeds later tasks. IIBA's BAPM task cards show it as an input to Plan Business Analysis Governance (3.3) and Plan Business Analysis Information Management (3.4) (IIBA task cards). It is also an input to Manage Stakeholder Collaboration (4.5) in Elicitation and Collaboration (Open Exam Prep). Many scenario questions hinge on this link: a weak engagement plan shows up later as missing approvals or silent stakeholders.

IIBA's own sample CBAP question follows the same pattern. A senior executive disagrees with the initiative's objectives, and the expected response is risk analysis (IIBA).

How to plan stakeholder engagement step by step

You plan stakeholder engagement by working through the three elements in order, then writing down the result as one approach.

Step 1. Perform stakeholder analysis

Stakeholder analysis is the work of naming stakeholders and describing the characteristics that change how you engage them. Start from the needs and the business analysis approach from task 3.1 (see Plan Business Analysis Approach). An org chart, process models and the scope model help you find people you would otherwise miss.

BABOK asks you to look at four characteristics for each stakeholder or group:

• Roles. What the person does in the organisation and on the change, and what knowledge they hold.
• Attitudes. How they feel about the goals, the business case, the solution and business analysis itself. Supporters, sceptics and people who do not care need different plans.
• Decision-making authority. Who approves, who can veto, and who only advises.
• Level of power or influence. Formal power from position and informal influence from networks, expertise or history.

A stakeholder list, a power/interest grid, an onion diagram or a RACI matrix are common ways to record this (Open Exam Prep). The format is free. What matters is that the analysis drives the next two steps.

Step 2. Define stakeholder collaboration

Defining collaboration means choosing how each stakeholder will take part in business analysis work. Consider timing and frequency, location (co-located or remote, time zones), tools, delivery method (workshop, one-on-one, survey, async review) and the stakeholder's own preferences. A busy executive may give 30 minutes at three decision points; a domain expert may join weekly workshops.

Step 3. Stakeholder communication needs

Communication needs describe what each stakeholder must receive, and what you need from them. Decide what to communicate, the channel, the level of detail, who is included, when and how often. Formality also matters: a regulator may need signed, versioned documents, while a delivery team may prefer a short chat update.

The output: stakeholder engagement approach

The stakeholder engagement approach is the documented result of the three steps: the stakeholder list with their characteristics, the planned collaboration, and the communication needs. It is a living plan. BABOK expects you to revisit it as stakeholders join, leave or change their attitude.

Worked example: replacing a payment provider

Here is how the task looks on a real-sized initiative. An online retailer replaces its card payment provider to cut fees and add a buy-now-pay-later option. The business analyst has a business analysis approach from task 3.1 (adaptive, two-week cycles) and the need: lower payment cost per order without hurting checkout conversion.

The analyst lists stakeholders from the org chart, the scope model and a 20-minute brainstorm with the project manager, then records the analysis:

Three decisions come straight from the table. First, the compliance officer has low interest in most topics but a veto on one, so the analyst books reviews at two gates instead of inviting them to every meeting. Second, the head of customer service is sceptical and well connected, so the analyst meets them one-on-one before any group workshop. Third, shoppers cannot be in the room, so their voice comes through usability tests and conversion data.

In week four the retailer's legal team adds a local consumer-credit regulator to the picture because of the buy-now-pay-later option. The analyst updates the stakeholder engagement approach the same day and tells the project manager, because the new stakeholder changes the governance gates planned in task 3.3.

What practitioners say about stakeholder engagement

Practitioners agree on one point: most engagement failures start with an incomplete or one-off stakeholder analysis.

• Aaron Whittenberger, writing on BA Times in 2014, lists improper stakeholder analysis as the first of eight elicitation mistakes. He notes that affected business lines are often unknown early, and one group speaking for another leaves voices missing (BA Times).
• Chris Adams on Modern Analyst describes stakeholder analysis as more than a list. For each person he records importance, influence, and the level, frequency and method of involvement, which then drives meeting plans (Modern Analyst).
• A 2014 Modern Analyst community post advises finding informal opinion leaders, offering quiet people one-on-one channels, and showing that their input changed the plan. The author sums it up: "Listening and putting yourself in the stakeholders shoes really works." (Modern Analyst community blog)
• Techcanvass trainers (2024) suggest learning whether a stakeholder thinks in process, data or results, batching questions into one message, and meeting difficult stakeholders privately so their views do not spread to the group (Techcanvass).
• A 2024 Axiata Digital Labs article by a practising analyst recommends mapping stakeholders on a stakeholder map during early elicitation and confirming status updates with them before treating them as final (Axiata Digital Labs).
• Adaptive US trainers advise tying update frequency to milestones and decision points, and revisiting the engagement plan through the whole life cycle (Adaptive US).

Common misconceptions about Plan Stakeholder Engagement

Most exam mistakes on task 3.2 come from mixing it up with neighbouring tasks or treating it as a one-time list.

• It is not a one-time kickoff activity. The approach is revisited when stakeholders, attitudes or scope change. A question that says a new stakeholder appeared mid-project usually wants you to update the engagement approach.
• The output is not called a communication plan. BABOK names one output: the stakeholder engagement approach. Communication needs are one element inside it.
• Planning is not managing. Task 3.2 plans the relationship. Keeping stakeholders engaged during the work is Manage Stakeholder Collaboration (4.5), and sending business analysis information is Communicate Business Analysis Information (4.4).
• Approval rules belong to governance. Who approves requirements and changes is defined in Plan Business Analysis Governance (3.3). Task 3.2 records decision-making authority as a stakeholder characteristic; 3.3 builds the process on top.
• Low interest does not mean ignore. On the power/interest grid, high-power, low-interest stakeholders are usually kept satisfied with short, targeted updates, not left out (Techcanvass). A veto holder with low interest still needs planned checkpoints.
• Attitude is not fixed. A sceptic can become a supporter and the reverse. Negative attitudes are risks to analyse, which is why Risk Analysis and Management is one of the techniques.

Practice Questions

These are original questions in the CBAP scenario style. Answers follow each question.

Question 1

A business analyst is starting an initiative to change how a bank handles loan applications. The sponsor supports the change. The head of internal audit shows little interest in the project but must approve any change to how customer data is stored. What should the business analyst do when planning stakeholder engagement?

• A. Leave the head of internal audit out of the plan because of low interest
• B. Invite the head of internal audit to every elicitation workshop
• C. Record the approval authority and plan targeted reviews at the points where data storage is decided
• D. Ask the sponsor to approve data storage changes instead

Answer: C. Stakeholder analysis covers decision-making authority and power, not only interest. A low-interest veto holder needs planned, targeted collaboration. A ignores a blocker, B wastes the stakeholder's time and lowers the chance they attend, and D bypasses real authority.

Question 2

Six weeks into an initiative, a new regulation names a government agency as a stakeholder that must review the solution. What should the business analyst do first?

• A. Update the stakeholder engagement approach to include the agency's role, authority and communication needs
• B. Continue with the current plan and inform the agency at go-live
• C. Start Manage Stakeholder Collaboration with the agency immediately
• D. Rewrite the business analysis approach from scratch

Answer: A. The stakeholder engagement approach is revisited when stakeholders change. Planning comes before managing collaboration (C). B risks late rejection, and D is far larger than the change requires.

Question 3

During stakeholder analysis, a business analyst learns that a regional director with strong influence over store managers disagrees with the initiative's objectives. Which action best fits Plan Stakeholder Engagement?

• A. Remove the regional director from the stakeholder list
• B. Treat the disagreement as a risk, plan one-on-one sessions to understand the concerns, and set communication to match
• C. Escalate to the sponsor and ask that the director be replaced
• D. Wait for elicitation to see whether the attitude changes

Answer: B. Attitude and influence are core parts of stakeholder analysis, and Risk Analysis and Management is a listed technique. Planning focused collaboration addresses the risk early. A and C avoid the problem, and D delays action that planning should cover.

For a full timed set of scenario questions on another IIBA exam, try the IIBA CBDA practice exam.

Related techniques and articles

These techniques do most of the work in task 3.2; see the BABOK techniques map by knowledge area for where else they appear.

• Stakeholder List, Map, or Personas (BABOK 10.43): the main recording tool for stakeholder analysis.
• Organizational Modelling and Scope Modelling: find stakeholders you would otherwise miss.
• Interviews, Workshops and Survey or Questionnaire: learn attitudes and preferences. The post on planning workshops covers how to set one up.
• Risk Analysis and Management: handle negative attitudes and missing decision makers.
• Lessons Learned: reuse what worked with the same stakeholders on earlier initiatives.

FAQ

What is the output of Plan Stakeholder Engagement?

The only output of BABOK task 3.2 is the stakeholder engagement approach. It contains the stakeholder list and their characteristics, how each stakeholder will collaborate, and their communication needs. It becomes an input to governance (3.3), information management (3.4) and Manage Stakeholder Collaboration (4.5).

What are the four parts of stakeholder analysis in BABOK?

BABOK asks the analyst to consider roles, attitudes, decision-making authority, and level of power or influence. Together they decide how much and what kind of engagement each stakeholder needs. Exam questions often hide the key fact in one of these four, such as a veto held by a low-interest person.

What is the difference between Plan Stakeholder Engagement and Manage Stakeholder Collaboration?

Plan Stakeholder Engagement (3.2) is a planning task that decides how to work with stakeholders. Manage Stakeholder Collaboration (4.5) is the ongoing work of keeping them engaged during business analysis activities. Task 4.5 uses the stakeholder engagement approach as an input.

Is a RACI matrix required for Plan Stakeholder Engagement?

No. BABOK does not require any specific format. A RACI matrix, a power/interest grid or an onion diagram are common choices for recording roles and authority, but the technique listed in BABOK is Stakeholder List, Map, or Personas.

How many CBAP questions cover stakeholder engagement planning?

IIBA does not publish per-task counts. BAPM is 14% of the 120-question CBAP exam, about 17 questions, and Plan Stakeholder Engagement is one of five BAPM tasks. Stakeholder topics also appear in Elicitation and Collaboration questions.

Sources

• IIBA: CBAP certification page
• IIBA: Plan Stakeholder Engagement task card (PDF)
• IIBA: All task cards, Business Analysis Planning and Monitoring (PDF)
• Viblo: BABOK summary, Business Analysis Planning part 2
• Open Exam Prep: Plan Stakeholder Engagement (Task 3.2)
• Open Exam Prep: Manage Stakeholder Collaboration (Task 4.5)
• BA Times: The Top 8 Mistakes in Requirements Elicitation (2014)
• Modern Analyst: What is stakeholder analysis and how does it benefit the business analyst?
• Modern Analyst community blog: Dealing with Difficult Stakeholders (2014)
• Techcanvass: How to Handle Difficult Stakeholders (2024)
• Axiata Digital Labs: The importance of stakeholder management in business analysis (2024)
• Adaptive US: How to Plan Stakeholder Engagement