Study guides / CAPM: Certified Associate in Project Management / Project roles & responsibilities
Project roles & responsibilities
CAPM: Certified Associate in Project Management · quick review
Who does what on a project: the sponsor, the project manager, the team, functional managers and the PMO, and how the organization's structure sets the project manager's authority.
The rules
- Sponsor: provides funding and backing, issues the charter, champions the project and handles escalations beyond the project manager's authority.
- Project manager: leads the team to meet the objectives; balances constraints, communicates, and integrates the work. Authority comes from the charter and the structure.
- Functional managers own people and resources in their department. Project team members do the work; in agile teams they self-organize.
- PMO types: supportive (templates, low control), controlling (requires compliance, moderate control), directive (manages projects directly, high control).
- Structures, from least to most project manager authority: functional → weak matrix → balanced matrix → strong matrix → projectized.
- Servant leadership (common in agile) means removing obstacles, shielding the team and supporting its growth rather than directing every task.
Common traps
- The sponsor, not the project manager, authorizes the project and owns the business case.
- In a functional or weak matrix organization, the project manager must negotiate for resources; they can't simply assign people.
- A PMO that only provides templates is supportive, not controlling.
How it's tested
Identifying who is responsible or has authority in a scenario, and naming the structure or PMO type described.
Practise it
The full lesson, worked examples and practice questions are in Tickmark, where every answer choice is explained.
Open the full lesson