SkarpChapter 4 of 21
Roles, Responsibilities, and Communication Across the Project Ecosystem
Step into the shoes of sponsors, product owners, functional managers, and business analysts to see how their decisions, conflicts, and communication styles shape project outcomes.
Mapping the Project Ecosystem
The Project Ecosystem
Projects sit inside a larger ecosystem of roles, governance, and operations. To manage a project well, you must know who decides what and how information should flow between them.
Key Definitions
A project is "A temporary endeavor undertaken to create a unique product, service, or result." A stakeholder is anyone who may affect, be affected by, or perceive themselves as affected by the project.
Roles in Focus
We will focus on: project manager, sponsor, product owner, product manager, functional manager, PMO types, business analyst, Scrum Master, and steering committee or governance board.
Life Cycle Context
We compare these roles in a predictive life cycle (scope, time, cost fixed early) versus an adaptive life cycle (agile/iterative, scope detailed each iteration).
What the Exam Cares About
CAPM questions often test who has which decision rights and how you tailor communications: who needs what information, how often, and in which format.
Core Roles: Project Manager, Sponsor, and PMO
Project Manager
The PM integrates all knowledge areas, manages the project plan and baselines, leads the team, and recommends changes. They coordinate and communicate, but usually do not approve the charter or major business changes.
Sponsor Role
The sponsor authorizes the project, approves the charter, provides funding, sets high-level scope and success criteria, and makes major business decisions and trade-offs.
Benefits Ownership
Exam tip: when asked who is ultimately accountable for ensuring expected benefits are realized, the best answer is usually the sponsor, not the project manager.
PMO Purpose
A PMO standardizes project practices, offers templates and tools, and may influence or control how projects are run across the organization.
PMO Types
Supportive (low control), Controlling (moderate control and compliance), and Directive (high control, directly manages projects) are the three PMO types to remember.
Product-Focused Roles: Product Owner, Product Manager, Scrum Master, BA
Product Owner
The product owner manages the product backlog, prioritizes work for value and risk, defines acceptance criteria, and accepts or rejects completed work.
Product Manager
The product manager owns product vision and roadmap, aligns the product with market and strategy, and works at a more strategic, cross-project level.
Scrum Master
The Scrum Master is a servant leader who coaches the team, facilitates Scrum events, and removes impediments but does not prioritize the backlog.
Business Analyst
The BA elicits, analyzes, and documents requirements and maintains the requirements traceability matrix linking requirements to deliverables.
Roles in Adaptive Work
In adaptive teams, the BA and PO collaborate to refine backlog items, while the Scrum Master focuses on process and the product manager on long-term product strategy.
Functional Manager and Steering Committee: Governance and Resources
Functional Manager Role
Functional managers lead departments, control staffing and technical standards, and often have strong authority over people assigned to projects.
Functional Manager Decisions
They decide who joins the project, how long they are available, approve time off, and set specialized practices the project must follow.
Steering Committee
A steering committee or governance board is a group of senior leaders who provide direction, approve major changes, and make go/kill decisions at phase gates.
Escalation Point
When issues affect strategy, portfolio priorities, or very large budgets, the PM and sponsor escalate to the steering committee for a decision.
Communication Needs
Functional managers and steering committees want concise updates focused on resource impacts, strategic alignment, and the specific decisions required.
Predictive vs Adaptive: Who Decides What?
Scenario Setup
You are building a new customer self-service portal. See how decisions change when you use a predictive life cycle versus an adaptive one.
Predictive: Roles in Action
BA gathers full requirements, PM plans schedule and cost, sponsor approves the baseline, functional manager assigns staff, and a change control board approves scope changes.
Predictive: Decision Rights
New features after baseline go through the CCB and sponsor; functional managers control staffing; PM and leads decide sequencing based on dependencies.
Adaptive: Roles in Action
Product owner manages and orders the backlog; Scrum Master facilitates; team pulls work into sprints; sponsor approves initial funding and high-level outcomes.
Adaptive: Decision Rights
The product owner chooses sprint content and accepts increments; the Scrum Master and team adjust process; governance still exists but is lighter and more outcome-focused.
Designing a Stakeholder Communication Approach
Analyze Stakeholders
First, assess each stakeholder’s power, interest, and attitude. This guides whether you manage them closely, keep them satisfied, or simply monitor.
Match Role to Needs
Sponsors and steering committees need high-level benefits and risk info; functional managers need resource and operations impacts; teams need detailed, day-to-day information.
Choose Channels
Use meetings, written reports, and visual boards. Predictive projects lean toward formal reports; adaptive projects favor frequent, visual communication.
Set Frequency
Decide how often to communicate: e.g., weekly status to sponsor, monthly steering committee reviews, daily stand-ups for the team.
Document the Plan
Capture who gets what, how, and when in the communications plan. When issues arise, revisit and update this plan and the stakeholder engagement plan.
Balancing Transparency and Confidentiality
Transparency Basics
You must be open about project status, risks, and key decisions. Hiding bad news is almost never correct; instead, escalate with options.
Sensitive Information
HR issues, confidential contract terms, and security-sensitive data require restricted sharing and careful wording in project communications.
Role-Based Sharing
Sponsors and steering committees may see more detail, while the wider team receives impact-focused summaries rather than confidential specifics.
Focus on Impacts
Describe what changes for the project (delays, cost, risk), not private reasons. Keep logs free of personal or legally risky details.
Exam Clue
If a PM shares a team member’s private situation in a status report, that is wrong. Correct behavior: report schedule impact and protect confidentiality.
Iterative Delivery as a Communication and Feedback Engine
Iterations as Communication
In adaptive life cycles, short iterations are communication tools: each sprint delivers a usable increment and a chance for stakeholders to react.
Feedback Loops
Sprint reviews and demos let stakeholders see working product, give feedback, and influence the product backlog quickly.
Predictive Contrast
Predictive projects focus on reports and milestone reviews against baselines; changes are harder because they disrupt established plans.
Reducing Uncertainty
By testing assumptions in small increments, iterations reveal issues early and limit the cost of wrong decisions to one short cycle.
Exam Angle
When the exam asks why to choose adaptive for uncertain work, one key reason is frequent feedback from short iterations that reduces uncertainty.
Thought Exercise: Tailoring Communication to Roles
Apply what you have learned by designing tailored communications for a simple scenario.
Scenario
You are managing a 6-month project to roll out a new internal expense-reporting tool. The organization uses a hybrid approach: high-level plan is predictive, but development uses 2-week sprints.
Key stakeholders:
- Sponsor: CFO (high power, high interest).
- Product owner: Finance manager.
- Functional manager: IT infrastructure lead (controls system administrators).
- Steering committee: CFO, CIO, HR director.
- Team: developers, testers, one business analyst.
A major integration risk has just materialized: the tool cannot connect to the legacy HR system as expected. You need to communicate this.
Your task
For each role or group below, write down (on paper or in your notes):
- Key message: What do they need to know in 1–2 sentences?
- Format/channel: Meeting, email, dashboard, stand-up announcement, etc.
- Level of detail: High-level impact only, or technical details as well?
Roles:
- Sponsor (CFO).
- Steering committee.
- Functional manager (IT infrastructure lead).
- Product owner.
- Team.
Reflect
After you draft your answers, compare them mentally to this pattern:
- Sponsor: short briefing, focused on impact to business case, timeline, and options.
- Steering committee: summary in next meeting pack, with recommended decision if a major change is needed.
- Functional manager: more technical detail and specific resource asks.
- Product owner: detailed impact on features, user experience, and backlog.
- Team: full technical detail so they can explore workarounds.
If your messages and channels match this pattern, you are thinking like the exam expects.
Quiz 1: Who Should Do What?
Test your understanding of roles and decision rights.
A project using Scrum is building a new mobile app. Mid-sprint, a senior executive asks the lead developer to add a new feature immediately. Who has the authority to decide whether this new feature is added to the next sprint, and what is the BEST immediate response?
- The Scrum Master; they should accept the request and add it to the current sprint to satisfy the executive.
- The product owner; the developer should direct the executive to discuss the new feature with the product owner for backlog prioritization.
- The project manager; they should update the schedule and instruct the team to start working on the new feature.
- The steering committee; the developer should request a special meeting to approve the new feature.
Show Answer
Answer: B) The product owner; the developer should direct the executive to discuss the new feature with the product owner for backlog prioritization.
In Scrum, the **product owner** owns the product backlog and decides feature priority. The best immediate response is to direct the executive to the product owner, who can add the feature to the backlog and prioritize it for a future sprint. The Scrum Master protects the team and process but does not prioritize features. The project manager and steering committee may influence scope at a higher level, but day-to-day backlog ordering is the product owner’s responsibility.
Quiz 2: Transparency vs Confidentiality
Check your understanding of balancing openness with privacy.
A key team member informs you they must take unexpected medical leave for three weeks. This will delay a critical deliverable. What is the MOST appropriate communication approach?
- Explain the medical situation in detail in the next status report so stakeholders understand why the delay is unavoidable.
- Do not mention the delay yet; wait to see if the team can catch up before alarming stakeholders.
- Inform stakeholders that a key resource will be unavailable, explain the schedule impact and options, but do not share personal medical details.
- Ask the sponsor to decide whether to reveal the medical details to the steering committee.
Show Answer
Answer: C) Inform stakeholders that a key resource will be unavailable, explain the schedule impact and options, but do not share personal medical details.
You must be transparent about impacts to scope, schedule, and cost, but protect personal confidentiality. The correct approach is to communicate that a key resource is unavailable, describe the schedule impact and options (e.g., reassign work, adjust dates), and avoid sharing private medical information. Hiding the delay or disclosing personal details broadly would both be inappropriate.
Key Roles and Concepts Review
Use these flashcards to reinforce core role definitions and communication ideas.
- Project sponsor
- Senior person who authorizes the project and charter, provides funding, champions the project, and is ultimately accountable for realizing business benefits and approving major changes.
- Project manager
- Person responsible for achieving project objectives, integrating all knowledge areas, leading the team, managing trade-offs, and recommending (but usually not unilaterally approving) major changes.
- Product owner
- Role that owns and manages the product backlog, prioritizes items for value and risk, defines acceptance criteria, and accepts or rejects increments in adaptive approaches.
- Product manager
- Role with a strategic focus on product vision, roadmap, and market alignment, often spanning multiple projects or releases beyond a single team’s backlog.
- Functional manager
- Manager of a department or function who controls staffing, performance evaluations, and functional standards, and negotiates resource availability for projects.
- PMO types
- Supportive (low control, provides templates/guidance), Controlling (moderate control, enforces standards), Directive (high control, directly manages projects and PMs).
- Scrum Master
- Servant leader who coaches the Scrum team and product owner, facilitates Scrum events, and removes impediments, but does not own backlog prioritization.
- Business analyst
- Role that elicits, analyzes, documents, and validates requirements, and helps maintain the requirements traceability matrix linking requirements to deliverables.
- Steering committee
- Group of senior stakeholders who provide governance, approve major changes, make go/kill decisions at phase gates, and resolve escalated conflicts.
- Adaptive life cycle communication
- Relies on short iterations, frequent demos, and visual boards to enable rapid feedback and continuous adjustment of scope via the product backlog.
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.
- steering committee
- A governance body of senior stakeholders that provides direction, approves major changes, and makes go/kill decisions for projects or programs.
- 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.
- 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.
- change control board (CCB)
- A formally chartered group responsible for reviewing, evaluating, approving, delaying, or rejecting changes to the project, and for recording and communicating such decisions.
- PMO (Project Management Office)
- An organizational structure that standardizes project-related governance processes and facilitates the sharing of resources, methodologies, tools, and techniques.
- requirements traceability matrix
- A grid that links product requirements from their origin to the deliverables that satisfy them.