Study guide
2.2 Plan Stakeholder Engagement (Task 3.2)
CCBA Certification of Capability in Business Analysis Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction & CCBA Exam Foundation
1.1 CCBA Exam Structure, Eligibility & IIBA Framework 1.2 The Business Analysis Core Concept Model (BACCM™) 1.3 Requirements Classification Schema & Architecture 1.4 CCBA Competency & Proficiency Levels (Level 2 — Skilled)
2 Chapter 2: Business Analysis Planning and Monitoring
2.1 Plan Business Analysis Approach (Task 3.1) 2.2 Plan Stakeholder Engagement (Task 3.2) 2.3 Plan Business Analysis Governance (Task 3.3) 2.4 Plan Business Analysis Information Management (Task 3.4) 2.5 Identify BA Performance Improvements (Task 3.5)
3 Chapter 3: Elicitation and Collaboration
3.1 Prepare for Elicitation (Task 4.1) 3.2 Conduct Elicitation (Task 4.2) 3.3 Confirm Elicitation Results (Task 4.3) 3.4 Communicate Business Analysis Information (Task 4.4) 3.5 Manage Stakeholder Collaboration (Task 4.5)
4 Chapter 4: Requirements Life Cycle Management
4.1 Trace Requirements (Task 5.1) 4.2 Maintain Requirements (Task 5.2) 4.3 Prioritize Requirements (Task 5.3) 4.4 Assess Requirements Changes (Task 5.4) 4.5 Approve Requirements (Task 5.5)
5 Chapter 5: Strategy Analysis
5.1 Analyze Current State (Task 6.1) 5.2 Define Future State (Task 6.2) 5.3 Assess Risks (Task 6.3) 5.4 Define Change Strategy (Task 6.4)
6 Chapter 6: Requirements Analysis and Design Definition — Modeling & Architecture
6.1 Specify and Model Requirements (Task 7.1) 6.2 Verify Requirements (Task 7.2) 6.3 Validate Requirements (Task 7.3) 6.4 Define Requirements Architecture (Task 7.4)
7 Chapter 7: Requirements Analysis and Design Definition — Design & Value
7.1 Define Design Options (Task 7.5) 7.2 Analyze Potential Value and Recommend Solution (Task 7.6) 7.3 Estimation Techniques & Solution Trade-Offs 7.4 Acceptance and Evaluation Criteria Definition
8 Chapter 8: Solution Evaluation
8.1 Measure Solution Performance (Task 8.1) 8.2 Analyze Performance Measures (Task 8.2) 8.3 Assess Solution Limitations (Task 8.3) 8.4 Assess Enterprise Limitations (Task 8.4) 8.5 Recommend Actions to Increase Solution Value (Task 8.5)
9 Chapter 9: Essential BABOK Techniques
9.1 Core Elicitation & Analysis Techniques 9.2 Process, Data & Non-Functional Requirements Modeling 9.3 Financial Analysis & Business Case Techniques 9.4 Prioritization & Scope Techniques 9.5 Root Cause & Decision Analysis Techniques
10 Chapter 10: Underlying Competencies & Perspectives
10.1 Analytical Thinking, Problem Solving & Systems Thinking 10.2 Behavioral Characteristics, Communication & Interaction Skills 10.3 Business Acumen, Solution Knowledge & BA Tooling 10.4 The Five BABOK Perspectives in Practice
11 Chapter 11: CCBA Exam Mastery & Scenario Strategy
11.1 Deconstructing CCBA Scenario Questions & BABOK Logic 11.2 Common Traps, Distractors & Subtle BABOK Distinctions 11.3 Comprehensive 8-Week Study Plan & Exam Day Strategy
2.2 Plan Stakeholder Engagement (Task 3.2)
Key Takeaways Explain This Topic AI
Stakeholder Engagement planning identifies all internal and external parties affected by a change, analyzes their characteristics, and defines tailored collaboration strategies.
The RACI matrix clarifies role accountability across BA deliverables by assigning exactly one Accountable individual per activity, supported by Responsible, Consulted, and Informed roles.
Stakeholder mapping models—including Power/Influence vs. Impact/Interest grids and the Stakeholder Onion Diagram—guide the depth and frequency of communication.
Effective engagement plans systematically account for geographical distribution, time zones, cultural nuances, language diversity, and communication channel preferences.
Stakeholder analysis is not a one-time kickoff event; it is an iterative task revisited throughout the initiative as stakeholder attitudes and organizational structures evolve.
Last updated: August 2026
2.2 Plan Stakeholder Engagement (Task 3.2)
Quick Summary: Task 3.2 defines how the business analyst will identify, analyze, and build productive working relationships with everyone impacted by a change. By examining stakeholder influence, authority, attitude, geographical distribution, and collaboration preferences , the BA creates a Stakeholder Engagement Approach that secures active participation, eliminates blind spots, and ensures smooth consensus throughout the project lifecycle.
Purpose and Scope of Stakeholder Engagement Planning
The primary objective of Task 3.2: Plan Stakeholder Engagement is to conduct a thorough stakeholder analysis and establish an effective plan for collaborating with stakeholders throughout the initiative. Requirements cannot be discovered in a vacuum; they reside in the minds, processes, and daily operational needs of stakeholders.
Failing to properly plan stakeholder engagement leads to severe project risks, including:
Overlooking critical subject matter experts (resulting in missing requirements discovered late in testing).
Misaligned expectations between business executives and technical delivery teams.
Political friction, stakeholder resistance, and low solution adoption upon deployment.
Identifying and Categorizing Stakeholders
The BABOK® Guide v3 defines standard stakeholder roles that business analysts interact with across initiatives: +-----------------------------------------------------------------------------+
- | BABOK Standard Stakeholder Roles |
- | |
- | [Business Sponsor] [Domain SME] [Implementation SME] |
- | - Funding & authority - Process & rule expert - Tech architect/dev/DBA |
- | |
- | [End User / Customer] [Operational Support] [Regulator] |
- | - Directly uses solution - Maintains & runs system- Enforces compliance |
- | |
- | [Project Manager] [Tester / QA] [Supplier / Vendor] |
- | - Manages scope & plan - Verifies requirements - External provider |
- +-----------------------------------------------------------------------------+
- Key Categorization Dimensions
Internal vs. External: Internal stakeholders belong to the enterprise (executives, branch staff, IT support), whereas external stakeholders reside outside the organizational boundary (clients, suppliers, regulatory bodies, trade unions).
Direct vs. Indirect Users: Direct users interact directly with the solution interface (e.g., call center agents using CRM); indirect users consume outputs or reports generated by the solution (e.g., financial auditors, senior executives reviewing BI dashboards).
Attitude and Receptivity: Positive advocates champion the change; neutral stakeholders require education; resistant stakeholders require targeted change management and active empathy to resolve legitimate concerns.
The Stakeholder Onion Diagram
The Stakeholder Onion Diagram visualizes stakeholder relationships and proximity to the solution across concentric layers:
Layer Ring Name Description & Typical Stakeholders Engagement Cadence
Layer 1 The Core Team Business Analysts, Project Managers, Solution Architects, Lead Developers, Scrum Masters. Directly responsible for creating the deliverables. Daily standups, continuous real-time collaboration
Layer 2 The Project Team Product Owners, Primary Domain SMEs, Dedicated Business Representatives, Core Quality Assurance Engineers. Directly involved in requirements elicitation and sprint validation. Bi-weekly workshops, sprint reviews, backlog grooming
Layer 3 The Affected Organization Frontline end-users, operational branch managers, helpdesk teams, finance, internal auditors. Impacted by business process changes. Monthly town halls, focused focus groups, UAT sessions
Layer 4 The External Environment External customers, suppliers, industry regulatory bodies (SEC, FDA, HIPAA), partner vendors, shareholders. Impacted by solution outputs. Formal milestone reviews, statutory compliance filings, surveys
Stakeholder Mapping: Power/Influence vs. Interest/Impact
The Power/Influence vs. Interest/Impact Grid is a foundational 2x2 matrix used to determine the appropriate communication and engagement strategy for each stakeholder group: High Power / Influence
- ^
- | [ KEEP SATISFIED ] [ MANAGE CLOSELY ]
- | - Executive Sponsors (Passive) - Project Business Sponsors
- | - Regulatory Compliance Officers - Key Business Unit Leaders
- | - Enterprise Security Architects - Lead Product Owners
- | ------------------------------------------------------------
- | [ MONITOR ] [ KEEP INFORMED ]
- | - Peripheral Vendors - Daily Operational End-Users
- | - Indirect Staff - Helpdesk Support Staff
- | - General Employees - Super-Users & Field Agents
- +-------------------------------------------------------------> High Interest / Impact
- Strategic Engagement Quadrants
High Power, High Interest (Manage Closely): Critical decision-makers and sponsors. The BA must engage them frequently through one-on-one briefings, secure their direct input on key trade-offs, and involve them in governance sign-offs.
High Power, Low Interest (Keep Satisfied): Influential executives and compliance authorities who have limited time for daily details. The BA must provide concise executive summaries, ensure regulatory constraints are honored, and avoid overwhelming them with technical jargon.
Low Power, High Interest (Keep Informed): Operational end-users and support teams deeply impacted by workflow changes. The BA must leverage their process insights during elicitation, keep them updated on rollout timelines, and solicit early usability feedback to build buy-in.
Low Power, Low Interest (Monitor): Peripheral stakeholders requiring minimal effort. The BA communicates via general project status newsletters or intranet updates.
The RACI Matrix in Business Analysis
The RACI Matrix establishes unambiguous governance and responsibility for business analysis activities and deliverables:
R — Responsible: The "doer" who performs the analysis and authors the deliverable (e.g., Lead Business Analyst drafting the Requirements Specification).
A — Accountable: The single individual who holds ultimate decision-making authority and ownership. If the deliverable fails or succeeds, accountability rests here. ( Golden Rule: Exactly one 'A' per activity. )
C — Consulted: Subject matter experts who provide vital two-way input and feedback before work is completed (e.g., Security Architect, Domain SME, Lead Developer).
I — Informed: Individuals who are updated one-way on progress, milestones, or finalized outcomes (e.g., Operations Staff, Helpdesk Leads).
Sample RACI Table for BA Deliverables
- BA Deliverable / Activity Business Sponsor Lead BA Domain SME Tech Architect Quality Assurance End User Rep
- Plan BA Approach A R C C I I
- Conduct Elicitation Workshops I A / R C C I C
- Model Business Processes I R A C I C
- Approve Requirements Baseline A C C C I I
- Conduct User Acceptance Testing I C C I R A
Caution
Common RACI Pitfalls to Avoid on the Exam:
Multiple 'A's: Assigning two Accountable roles creates finger-pointing and decision paralysis.
No 'A': Tasks with zero Accountable owners stall indefinitely.
Too Many 'C's: Over-consulting creates endless consensus meetings and delivery delays.