SkarpChapter 15 of 20
Business Analysis Roles, Stakeholders, and Communication
Step into the business analysis perspective to see how BA roles interact with project stakeholders and how effective communication underpins successful change.
Business Analysis in the CAPM Landscape
Where BA Fits in CAPM
Business analysis is a full CAPM domain: Business Analysis Frameworks (27%), alongside Fundamentals, Predictive, and Agile. It is central, not optional.
Project vs BA Focus
A project is "A temporary endeavor undertaken to create a unique product, service, or result." BA focuses on why, what value, and whether needs are really met.
Why This Module Matters
You must distinguish BA vs PM vs PO, apply the canonical stakeholder definition, plan stakeholder communication, and match techniques to scenarios.
Link to Earlier Modules
From agile: BA supports refining the product backlog. From hybrid: BA insight helps decide which work to run predictively vs adaptively.
Exam Angle
CAPM questions often hide BA content inside PM or agile stories. Your advantage is spotting the BA decision hiding inside communication and stakeholder items.
BA vs PM vs Product Owner: Who Does What?
BA: Value and Requirements
BA focuses on value and requirements: current vs future state, eliciting and documenting requirements, and using a requirements traceability matrix.
PM: Delivering the Project
PM focuses on delivering the project: scope, schedule, cost, risk, and managing the work breakdown structure and work packages.
PO: Product and Backlog
PO focuses on product value: owns the product backlog, sets vision, and defines acceptance criteria for features and increments.
Overlap in Practice
In small teams, one person may do BA, PM, and PO work. For CAPM questions, assume roles are distinct unless the scenario states otherwise.
Exam Signal Words
Questions about understanding needs, refining requirements, or evaluating solution fit usually indicate BA responsibilities, even if the title is PM.
BA Role in Predictive vs Adaptive Life Cycles
BA in Predictive Life Cycles
In a predictive life cycle, BA work is front-loaded: big requirements documents, early sign-offs, and heavy use of traceability to manage changes.
BA in Adaptive Life Cycles
In an adaptive life cycle, BA work is continuous: user stories, just-in-time detail, frequent collaboration with the PO, and evolving acceptance criteria.
Hybrid BA Work
Hybrid mixes both: high-level needs set early, detailed requirements refined iteratively for each release or iteration.
Exam Clues
Fixed scope + big up-front documents = predictive BA. Changing priorities + short iterations = adaptive BA behaviors.
Constant BA Purpose
Across all life cycles, the BA’s purpose is stable: ensure solutions align with business needs; only timing and style change.
Stakeholders: Canonical Definition and Analysis
Canonical Stakeholder Definition
A stakeholder is "An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by" project decisions or outcomes.
Hidden Stakeholders
Stakeholders include anyone who perceives impact: users, sponsors, compliance, security, partners, even if the team has not engaged them yet.
Power/Interest Grid Basics
Analyze stakeholders by power and interest: manage closely, keep satisfied, keep informed, or monitor, depending on their quadrant.
More BA Dimensions
BA also considers stakeholder attitude, role in requirements (source, reviewer, approver, tester), and business vs technical knowledge.
Exam Trap
If someone perceives they are affected, they are a stakeholder, even if the team thinks impact is small or indirect.
Planning Stakeholder Communication as a BA
Purpose of BA Communication Planning
BA communication planning supports requirements, analysis, and solution evaluation, not just general project status.
Segment Stakeholders
Start with a stakeholder list segmented by role and power/interest. This shapes what you say and how often you engage each group.
Tailor Message Content
Executives want outcomes and decisions; users want workflow impacts; technical teams need detailed requirements and data definitions.
Timing and Cadence
Predictive favors scheduled reviews and sign-offs; adaptive favors frequent, lightweight touchpoints like backlog refinement and reviews.
Feedback and Ownership
Define how stakeholders give feedback and who owns each communication: BA, PM, PO, or SMEs.
Communication Channels and BA Techniques
Channels vs Techniques
Distinguish channels (verbal, written, visual) from BA techniques (interviews, workshops, observation, surveys, prototyping).
Interviews and Workshops
Use interviews for depth and sensitivity; workshops for alignment and conflict resolution across multiple stakeholders.
Observation and Surveys
Use observation to uncover real work and workarounds; surveys to reach many, distributed stakeholders for broad input.
Prototypes and Visuals
Use prototypes and wireframes when text is confusing and you need stakeholders to react to something concrete.
Choosing the Next Step
Match technique to stakeholder characteristics and information needs; exam questions often hinge on this choice.
Mini Case: Matching Techniques to Stakeholders
Scenario Overview
Project: improve customer onboarding at a bank. Stakeholders include an executive sponsor, managers, front-line staff, compliance, and IT architect.
Executive Sponsor & Managers
Use concise visual briefings for the sponsor; use process-focused workshops and follow-up interviews with branch managers for feasibility input.
Front-Line Staff
Observe real work, run small-group interviews, and test low-fidelity prototypes to capture pain points and validate practicality.
Compliance and Traceability
With compliance, use interviews and document reviews to identify regulatory requirements and link them in a traceability matrix.
IT Architect
Run technical workshops and data model reviews with the architect to clarify integrations and nonfunctional requirements.
How BA Communication Changes Over the Life Cycle
Early Phase Communication
Early on, BA communication is exploratory: interviews, high-level process maps, and stakeholder identification and analysis.
Requirements and Design
Predictive uses structured workshops and sign-offs; adaptive uses continuous backlog refinement and evolving acceptance criteria.
Build and Implementation
During build, BAs clarify requirements, resolve ambiguities, support test design, and prepare users for upcoming changes.
Solution Evaluation
BAs compare pre- and post-implementation metrics, share dashboards, and conduct segmented evaluation across user groups.
Align with Life Cycle
On the exam, choose BA communications that fit the current life cycle phase and whether the approach is predictive, adaptive, or hybrid.
Thought Exercise: Power/Interest and Communication Choices
Work through this exercise to practice stakeholder analysis and communication planning.
Scenario
You are the BA on a project to introduce a new self-service portal for university students. Stakeholders include:
- Vice Chancellor for Academic Affairs
- IT support desk manager
- Student representatives
- Data privacy officer
- Finance department (handles tuition billing)
Your tasks
- For each stakeholder, quickly rank their power (low/medium/high) and interest (low/medium/high) in the portal.
- Place them mentally on a power/interest grid and choose one of the four strategies: manage closely, keep satisfied, keep informed, monitor.
- For each stakeholder, decide:
- One primary communication objective (e.g., obtain approval, gather requirements, ensure compliance).
- One primary technique (e.g., executive briefing, workshop, interview, survey, prototype demo).
Reflect
- Which stakeholders did you classify as "manage closely" and why?
- Did any stakeholder surprise you when you considered their power or interest?
- If you discovered late that students were using workarounds to avoid the portal, how would that change your communication plan?
You do not need to write full answers now, but try to form a clear mental picture. This is the same reasoning you will apply to “What should the BA do next?” questions on your next mock exam and in your spaced review items.
Quiz 1: Roles and Stakeholders
Test your understanding of BA vs PM vs PO and the stakeholder definition.
A project team is building a new claims system. The product owner prioritizes features, the project manager tracks schedule and cost, and another team member focuses on understanding current workflows, eliciting detailed requirements, and evaluating whether the released features actually improve processing time. Which role best describes that third team member's primary responsibilities?
- Project manager
- Business analyst
- Product owner
- Scrum master
Show Answer
Answer: B) Business analyst
The described work is classic business analysis: understanding current workflows, eliciting detailed requirements, and evaluating whether features improve processing time (solution evaluation). The PM focuses on schedule and cost, and the PO focuses on prioritizing the product backlog and defining acceptance criteria. A scrum master facilitates the agile process but does not usually lead requirements analysis.
Quiz 2: Communication Techniques and Life Cycles
Apply your knowledge of stakeholder communication and technique selection.
In a predictive life cycle project, the BA has completed initial requirements workshops. Several months later, during system testing, end users report that their actual workflow includes extra approval steps that were never documented. What is the most appropriate next action for the BA?
- Schedule a sprint review to demonstrate the current system and gather feedback.
- Update the communication plan to increase the frequency of status emails to all stakeholders.
- Conduct targeted observation or shadowing of end users, then update the requirements and traceability matrix to reflect the real workflow.
- Ask the project manager to fast-track a change request that adds the missing approval steps without further analysis.
Show Answer
Answer: C) Conduct targeted observation or shadowing of end users, then update the requirements and traceability matrix to reflect the real workflow.
The issue is a gap between documented and actual workflow, often uncovered by observation. The best BA action is to observe real work, refine requirements, and update the requirements traceability matrix so the change is properly analyzed and tested. A sprint review (A) is specific to adaptive life cycles, more status emails (B) do not address the root cause, and fast-tracking changes without analysis (D) risks introducing defects or noncompliance.
Key Terms Review
Use these flashcards to reinforce core definitions and concepts relevant to BA roles, stakeholders, and communication.
- project
- A temporary endeavor undertaken to create a unique product, service, or result.
- stakeholder
- An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
- predictive life cycle
- A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
- adaptive life cycle
- A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
- product backlog
- An ordered list of everything that is known to be needed in the product, managed by the product owner.
- requirements traceability matrix
- A grid that links product requirements from their origin to the deliverables that satisfy them.
- acceptance criteria
- A set of conditions that is required to be met before deliverables are accepted.
- Power/Interest Grid – High Power, High Interest
- Stakeholders who should be managed closely with frequent, high-quality communication and involvement in key decisions.
- BA vs PM Focus (One-Sentence Contrast)
- The BA focuses on understanding needs and defining/evaluating solutions; the PM focuses on planning and controlling delivery of the project.
- Common BA Communication Techniques
- Interviews, workshops, observation, surveys/questionnaires, and prototyping/wireframes, selected based on stakeholder characteristics and information needs.
Key Terms
- project
- A temporary endeavor undertaken to create a unique product, service, or result.
- stakeholder
- An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
- work package
- The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.
- product backlog
- An ordered list of everything that is known to be needed in the product, managed by the product owner.
- schedule variance
- A measure of schedule performance expressed as the difference between earned value and planned value.
- product owner (PO)
- A role, primarily in adaptive life cycles, responsible for maximizing product value by managing and prioritizing the product backlog and defining acceptance criteria.
- acceptance criteria
- A set of conditions that is required to be met before deliverables are accepted.
- adaptive life cycle
- A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
- power/interest grid
- A stakeholder analysis tool that categorizes stakeholders based on their level of power (influence) and interest in the project outcomes.
- solution evaluation
- BA activity of defining and comparing pre- and post-implementation performance metrics to determine whether a solution delivered expected business value.
- business analyst (BA)
- A role that focuses on understanding business needs, eliciting and analyzing requirements, and evaluating whether solutions deliver expected business value.
- predictive life cycle
- A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
- work breakdown structure
- A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
- requirements traceability matrix
- A grid that links product requirements from their origin to the deliverables that satisfy them.