2.2 Plan Stakeholder Engagement (Task 3.2)

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

1. 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).
2. 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).
3. 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:

---

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

[!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.