SkarpChapter 14 of 20
Stakeholder Communication and Collaboration Across Predictive and Agile
Bring together everything you’ve learned about stakeholders and approaches to see how communication strategies shift between predictive and adaptive projects. You’ll practice matching communication tools and cadences to different stakeholder needs and life cycles.
Big Picture: Why Communication Changes Across Predictive and Agile
Why This Module Matters
You will connect stakeholder ideas with project approaches, and see how communication expectations change between predictive and adaptive (agile) life cycles.
Key Definitions
A project is "A temporary endeavor undertaken to create a unique product, service, or result." A stakeholder is anyone who may affect or be affected by project outcomes.
Life Cycles and Communication
In a predictive life cycle, scope, time, and cost are fixed early, so communication is more formal and document‑heavy. In adaptive life cycles, communication is frequent and conversational.
Exam Angle
On CAPM, many questions ask: given this context and stakeholder, which communication method or artifact is most appropriate? This module builds that decision skill.
Stakeholder Information Needs and the Communication Plan
Two Core Artifacts
Use the stakeholder register to know who people are and what they care about, and the communications management plan to define how you will keep them informed.
What the Plan Covers
The communications plan defines stakeholder groups, information needs, formats and channels, frequency, senders, receivers, and escalation and feedback paths.
Predictive vs Adaptive Planning
Predictive projects document communication in detail and baseline it; agile teams often use lighter tools like working agreements or a simple engagement plan.
Exam Tip
On CAPM, the best answer is not "communicate more" but "communicate appropriately": right content, right audience, right cadence.
Channels and Methods: Formal vs Informal, Push vs Pull, Synchronous vs Asynchronous
Formality Spectrum
Formal communication is structured and documented (reports, change requests). Informal is quick and flexible (chats, whiteboards).
Push, Pull, Interactive
Push sends info to recipients; pull lets them fetch it (e.g., dashboards); interactive is real‑time two‑way exchange like meetings or workshops.
Timing: Sync vs Async
Synchronous methods happen in real time (stand‑ups, calls). Asynchronous methods happen at different times (email, recorded updates).
Predictive vs Agile Mix
Predictive often uses formal, push, asynchronous channels. Agile emphasizes interactive, often informal, synchronous communication plus pull via visual boards.
Predictive Communication Patterns and Artifacts
Predictive Focus
Predictive communication supports controlling against fixed scope, schedule, and cost baselines and managing expectations when changes occur.
Key Predictive Events
Common events: phase‑gate reviews, milestone sign‑offs, periodic status reports, and change control board meetings.
Core Artifacts
Artifacts include detailed status reports, change logs, and a requirements traceability matrix linking requirements to deliverables.
Exam Signal
If a scenario mentions baselines, heavy regulation, and long phases, expect formal reports and scheduled reviews, not agile ceremonies.
Agile Communication: Ceremonies, Information Radiators, and Feedback Loops
Agile Communication Goals
Adaptive life cycles use communication to get rapid feedback, maintain transparency, and enable collaboration as scope evolves.
Core Ceremonies
Key agile events: daily stand‑ups, iteration planning, reviews/demos for stakeholders, and retrospectives for continuous improvement.
Information Radiators
Boards and charts (task boards, Kanban, burn‑down) show live work and status, letting stakeholders "pull" information any time.
Backlog vs Communication
A product backlog lists needed product work; ceremonies and visual boards are how teams communicate about that work.
Visualizing Information Radiators: Task Boards, Burn‑Downs, and Kanban
Scrum Room: Task Board
Picture a board with columns like "To Do", "In Progress", "Testing", "Done" and cards for each user story. Anyone can see where work is flowing or stuck.
Scrum Room: Burn‑Down Chart
Above the board, a burn‑down chart shows remaining work versus days in the sprint. A smooth downward line suggests the team will finish on time.
Kanban Room: Workflow and WIP
A Kanban board has more workflow steps (Requested, Ready, Dev, Review, Testing, Release) and WIP limits at the top of each column.
Kanban Room: Cumulative Flow
A cumulative flow diagram shows how many items are in each state over time, highlighting bottlenecks when one band grows too thick.
Thought Exercise: Matching Stakeholders to Channels
Use this short exercise to practice mapping stakeholder needs to communication approaches. Think through your answers before checking against the guidance.
Scenario A
- Stakeholder: Executive sponsor
- Context: Predictive construction project; high budget; strict regulatory oversight; sponsor is very busy and travels a lot.
Questions for you:
- What type of information does the sponsor mainly need?
- Which channels and cadence make sense?
- Should communication be more formal or informal?
Pause and answer mentally.
Sample reasoning:
- Sponsor needs high‑level status, risks, issues, and decisions required; not task‑level detail.
- Channels: concise monthly status reports (push, formal) plus a quarterly steering committee meeting (interactive). Use dashboards as pull information.
- Because of regulation and budget, lean formal: documented reports, clear decisions, and audit trail.
Scenario B
- Stakeholder: Lead user representative
- Context: Adaptive software product with Scrum; 2‑week sprints; product evolves based on user feedback.
Questions for you:
- Which agile events should this user attend or be invited to?
- What visuals or artifacts help them understand progress?
Sample reasoning:
- Invite them to sprint reviews/demos for feedback, occasionally to backlog refinement for prioritization, and possibly to planning for context.
- Show the product backlog, the sprint goal, and the team’s board so they can see what is coming and what is done.
As you do more practice, try designing a mini communication plan for 3–4 stakeholder types in both predictive and agile contexts.
Quiz 1: Predictive vs Agile Communication Choices
Try this single‑question quiz to check your understanding of how context shapes communication.
A project manager is leading a highly regulated, fixed‑price project with a detailed scope defined upfront. The sponsor wants to ensure tight control of changes and clear documentation for audits. Which communication approach is MOST appropriate?
- Invite the sponsor to daily stand‑ups and rely mainly on a Kanban board for status.
- Send informal instant‑message updates whenever major tasks finish; avoid formal reports to stay agile.
- Establish regular formal status reports, phase‑gate reviews, and documented change control board meetings.
- Use only a product backlog and sprint reviews to keep the sponsor updated on scope changes.
Show Answer
Answer: C) Establish regular formal status reports, phase‑gate reviews, and documented change control board meetings.
This is a classic **predictive** context: fixed price, detailed upfront scope, and heavy regulation. The best answer emphasizes **formal, documented communication** such as regular status reports, phase‑gate reviews, and CCB meetings (option C). The other options lean too heavily on agile practices or are too informal for audit needs.
Quiz 2: Information Radiators and Stakeholder Needs
This quiz focuses on agile information radiators and stakeholder expectations.
An agile team wants to improve transparency for a group of remote stakeholders who frequently ask, "What is the team working on right now, and are we on track this iteration?" Which combination BEST addresses this need?
- A detailed requirements traceability matrix updated at the end of the project.
- A shared online task board showing current work and a sprint burn‑down chart updated daily.
- Monthly narrative status reports summarizing tasks completed and lessons learned.
- A one‑time kickoff presentation explaining the product backlog and release roadmap.
Show Answer
Answer: B) A shared online task board showing current work and a sprint burn‑down chart updated daily.
Remote stakeholders want **current, iteration‑level visibility**. A shared online task board plus a daily updated burn‑down chart are classic **information radiators** that provide pull‑based, near real‑time transparency (option B). The other options are too infrequent or not focused on current work.
Hybrid Life Cycles: Blending Predictive and Agile Communication
Hybrid Reality
Many projects mix predictive and agile. Communication must serve both: high‑level governance and low‑level iterative delivery.
Macro vs Micro
Predictive at macro: budgets, milestones, compliance. Adaptive at micro: detailed requirements and design emerging within iterations.
Two Audiences
Executives/regulators get formal reports and roadmaps; product owners/users/teams use agile ceremonies and boards for daily work.
Translate Between Worlds
When agile work reveals changes, update backlogs and also communicate milestone or budget impacts using predictive‑style summaries.
Key Terms and Concepts Review
Use these flashcards to reinforce key definitions and distinctions that often appear on the CAPM exam.
- 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.
- information radiator (concept)
- A highly visible display (such as a task board or burn‑down chart) that presents up‑to‑date information about the project so stakeholders can quickly understand status without asking.
- push vs pull communication
- Push sends information directly to recipients (e.g., email). Pull stores information in a place stakeholders access when needed (e.g., dashboards, wikis, boards).
- formal vs informal communication
- Formal is structured and documented (reports, sign‑offs); informal is quick and flexible (chats, ad‑hoc discussions). Predictive leans formal; agile leans informal plus visual.
- interactive communication
- Two‑way real‑time communication such as meetings, workshops, and video calls, essential for agile collaboration and resolving complex issues.
Mini Scenario Lab: Adjusting Communication for Better Engagement
Apply what you have learned by analyzing two short scenarios and deciding on communication adjustments.
Scenario 1: Predictive Project, Disengaged Users
- A predictive ERP implementation is in the design phase.
- End users are invited only to occasional requirement sign‑off meetings.
- Late in testing, users complain that the system does not fit their workflow.
Your task:
- Identify the communication problem in one sentence.
- Propose two changes to communication to reduce this risk on future projects.
Sample reasoning:
- Problem: Users had infrequent, formal, late‑stage communication, so feedback arrived too late.
- Possible adjustments:
- Add interactive workshops and prototyping sessions earlier in the life cycle.
- Provide regular progress demos of key workflows, even in a predictive context, to gather early feedback.
Scenario 2: Agile Project, Overwhelmed Sponsor
- A Scrum team invites the sponsor to daily stand‑ups and shares every technical detail.
- The sponsor feels overwhelmed and starts skipping all meetings, including sprint reviews.
Your task:
- What is misaligned between stakeholder needs and communication?
- Suggest two adjustments.
Sample reasoning:
- Misalignment: Sponsor is receiving too much low‑level, frequent information instead of concise, outcome‑focused updates.
- Adjustments:
- Limit sponsor participation to sprint reviews and a monthly high‑level summary of outcomes and risks.
- Use a simple dashboard or one‑page status view aligned with business goals instead of detailed task‑level discussions.
Use these patterns when you later take Skarp diagnostics and mock exams: look for mismatches between stakeholder needs, life cycle, and communication style, then choose the option that best realigns them.
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.
- product backlog
- An ordered list of everything that is known to be needed in the product, managed by the product owner.
- pull communication
- Communication where information is placed in a central location and stakeholders access it when needed, such as dashboards, wikis, or Kanban boards.
- push communication
- Communication where information is sent directly to specific recipients, such as email or status reports.
- 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.
- formal communication
- Structured, often documented communication used for governance or compliance, such as official reports and sign‑offs.
- information radiator
- A highly visible, easily accessible display of key project information (such as a task board or burn‑down chart) that keeps status transparent for the team and stakeholders.
- 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.
- informal communication
- Unstructured, quick communication such as chats, ad‑hoc discussions, and instant messages.
- interactive communication
- Two‑way, real‑time communication such as meetings, workshops, or video calls.
- requirements traceability matrix
- A grid that links product requirements from their origin to the deliverables that satisfy them.