Study guide

4.1 Project Roles and Responsibilities

CAPM Certified Associate in Project Management Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & CAPM Exam Overview

1.1 About the CAPM Exam 1.2 PMBOK 7th Edition Overview 1.3 Exam Content Outline (ECO) 1.4 CAPM vs. PMP: Understanding the Differences

2 Chapter 2: Project Life Cycles and Processes (Domain 1, Tasks 1-2)

2.1 Projects, Programs, and Portfolios 2.2 Project Life Cycle Phases 2.3 The Five Process Groups 2.4 The Ten Knowledge Areas

3 Chapter 3: Project Management Planning (Domain 1, Task 2)

3.1 The Project Management Plan 3.2 Scope Management and the WBS 3.3 Schedule Management 3.4 Cost Management and Earned Value 3.5 Quality Management

4 Chapter 4: Project Roles, Responsibilities, and Ethics (Domain 1, Tasks 3-4)

4.1 Project Roles and Responsibilities 4.2 Leadership and Emotional Intelligence 4.3 Risk Management Fundamentals 4.4 PMI Code of Ethics and Professional Conduct 4.5 Problem-Solving Tools and Techniques

5 Chapter 5: Resource, Communication, and Stakeholder Management (Domain 1, Tasks 2-3)

5.1 Resource Management 5.2 Communications Management 5.3 Stakeholder Management 5.4 Procurement Management 5.5 Issues, Risks, Assumptions, and Constraints

6 Chapter 6: Predictive, Plan-Based Methodologies (Domain 2)

6.1 When to Use a Predictive Approach 6.2 WBS, Work Packages, and Activity Definition 6.3 Predictive Project Controls and Artifacts 6.4 Critical Path and Schedule Calculations

7 Chapter 7: Agile Frameworks and Methodologies (Domain 3, Tasks 1-3)

7.1 When to Use an Adaptive (Agile) Approach 7.2 The Scrum Framework 7.3 Kanban, XP, and SAFe 7.4 Agile Planning, Estimation, and Metrics 7.5 Agile Project Controls and Artifacts

8 Chapter 8: Business Analysis Roles and Stakeholder Communication (Domain 4, Tasks 1-2)

8.1 Business Analysis Roles and Responsibilities 8.2 Stakeholder Communication in Business Analysis 8.3 Business Case and Needs Assessment

9 Chapter 9: Requirements Gathering and Product Roadmaps (Domain 4, Tasks 3-4)

9.1 Requirements Gathering Approaches 9.2 Requirements Traceability Matrix 9.3 Product Roadmaps

10 Chapter 10: BA Methodologies and Requirements Validation (Domain 4, Tasks 5-6)

10.1 Business Analysis in Predictive and Agile Approaches 10.2 Acceptance Criteria and Requirements Validation 10.3 Business Analysis Tools and Techniques Summary

4.1 Project Roles and Responsibilities

Key Takeaways Explain This Topic AI

The project sponsor funds the project, signs the charter, resolves escalated issues, and accepts final deliverables; the PM never signs their own charter

The project manager is accountable for outcomes but borrows resources; authority depends heavily on organizational structure

PMOs come in three flavors — supportive (low control), controlling (moderate, requires compliance), and directive (high, runs the projects)

Functional managers own the people and the budget for their department; in a functional org the PM is only a coordinator or expediter

On the CAPM, the projectized structure gives the PM the most authority and the functional structure gives the least

Last updated: June 2026

Why Roles Matter on the CAPM

The Certified Associate in Project Management (CAPM) exam contains 150 questions answered in 3 hours , and the Project Management Fundamentals and Core Concepts domain is the single largest block at roughly 36% of the test. A large share of those items are role-based scenarios: "Who should the PM go to?" or "Who has authority to approve X?" If you can map a situation to the correct role, you can usually eliminate two wrong answers immediately.

The Project Sponsor

The project sponsor is a senior executive who provides the money and political backing for the project. The sponsor is the business owner of the outcome, not the day-to-day manager.

  • Sponsor responsibilities
  • Authorizes the project and signs the project charter (the PM drafts it; the sponsor signs it)
  • Provides funding and approves the budget
  • Removes organizational obstacles the PM cannot resolve alone
  • Resolves escalated issues and approves major scope changes (often via a Change Control Board)
  • Accepts final deliverables and authorizes formal closure
  • The Project Manager

The project manager (PM) is assigned by the performing organization to lead the team and is accountable for project outcomes even though they rarely own the resources outright.

  • Responsibility Sponsor Project Manager
  • Funding Provides Manages within budget
  • Charter Signs / approves Develops the content
  • Major scope change Approves Runs the change process
  • Escalated issue Resolves Escalates after analysis
  • Day-to-day work Not involved Leads and directs
  • PMI Talent Triangle (renamed 2022)

PMI updated the Talent Triangle, replacing the old labels. The CAPM still tests the three competency domains — just by their current names:

  • Current name Former name Focus
  • Ways of Working Technical PM Predictive, agile, hybrid, design thinking
  • Power Skills Leadership Communication, collaboration, empathy, problem-solving
  • Business Acumen Strategic & Business Mgmt Industry/organizational knowledge, strategic alignment
  • The Project Team and the PMO

The project team is everyone doing the work. Teams can be dedicated (full-time), part-time , virtual (geographically dispersed), cross-functional , or self-organizing (common in agile).

A Project Management Office (PMO) standardizes governance and shares methods, tools, and resources. Memorize the three types — they are a recurring trap because the difference is the degree of control :

  • PMO type Control What it does
  • Supportive Low Provides templates, training, lessons learned; a consultative repository
  • Controlling Moderate Provides support and requires compliance with frameworks and governance
  • Directive High Directly manages the projects and assigns the PMs
  • Organizational Structures

The structure decides how much authority the PM actually has — this is the most-tested concept in the section.

  • Structure PM authority Resource availability PM title
  • Functional Little / none Little / none Coordinator or expediter (part-time)
  • Weak matrix Low Low Coordinator (part-time)
  • Balanced matrix Low–moderate Low–moderate Project manager (full-time)
  • Strong matrix Moderate–high Moderate–high Project manager (full-time)
  • Projectized High–near total High–near total Project manager (full-time)

Exam trap: In a functional organization the functional manager controls the people and budget; the PM is merely a coordinator. A project expediter has no decision authority (a staff assistant), while a project coordinator has limited authority. In a projectized organization the PM has the most authority and team members often have no functional "home" to return to. Matrix structures sit in between.

How the Roles Interact in Practice

The CAPM rarely asks you to recite a definition; instead it drops you into a scenario and asks who should act. Three patterns recur and are worth rehearsing. First, when a problem is inside the PM's authority — reassigning a task, adjusting a non-baseline detail, coaching a team member — the answer is that the project manager handles it directly rather than running to the sponsor. Going to the sponsor for routine matters signals weak ownership and is a wrong answer.

Second, when an obstacle is organizational — a functional manager will not release a promised resource, or another department blocks progress — the PM should first attempt to resolve it through negotiation and only then escalate to the sponsor , who has the standing to remove cross-organizational roadblocks.

Third, when a request would change the approved baseline (scope, budget, or schedule), the PM does not simply say yes. The PM logs the request, performs integrated change control , and routes it to the Change Control Board (CCB) or the sponsor for a decision. A favorite distractor is the option where the PM unilaterally approves a customer's "small" scope addition; on the CAPM that is scope creep and is incorrect.

Remember the difference between accountability and responsibility : the PM is accountable for the overall result and cannot delegate that accountability, but specific work responsibilities are assigned across team members, often documented in a RACI chart (Responsible, Accountable, Consulted, Informed). In a RACI matrix there is exactly one Accountable party per activity, while multiple people may be Responsible, Consulted, or Informed. Functional managers, meanwhile, are frequently the Consulted experts who supply staff and approve their availability even in matrix environments where the PM runs the day-to-day work.