3.4 Project Roles and Responsibilities
Key Takeaways
- Distinct project roles exist so authority, accountability, and specialist contribution are clear: users, project team members, the project manager, the steering group/board, the product owner, and the sponsor.
- Collapsing roles into one person creates conflicts of interest and weak accountability when problems emerge.
- Users define needs and accept outputs on fitness for use; they do not set organisational strategy alone.
- Steering groups and boards make collective continue, change, and stop decisions rather than managing tasks.
- The product owner prioritises product value within an agreed vision and does not replace sponsor accountability for the investment.
Why Distinct Roles Exist
The APM PMQ learning outcomes require you to understand why there are distinct roles within project management and to know the responsibilities of each role, including users, project team members, the project manager, the project steering group/board, and the product owner. You must also understand differences between the project manager and the project sponsor throughout the project.
Distinct roles exist because a project simultaneously needs:
- Strategic ownership of why the investment exists (sponsor / board).
- Day-to-day management of delivery (project manager).
- Specialist execution (team members and suppliers).
- Operational and user insight so outputs are usable and adopted (users / user representatives).
- In iterative work, continuous value prioritisation (product owner).
Collapsing these roles into one person creates conflicts of interest (for example, the person chasing a deadline also signing off that the business case still holds) and weak accountability when things go wrong.
Role Map for APM PMQ
Use the following RACI-style map as a study anchor. Exact labels vary by organisation, but the responsibilities are what the exam tests.
| Role | Primary accountability | Typical authority | Usually does not |
|---|---|---|---|
| Project sponsor | Business case ownership; continued justification; senior direction and funding advocacy | Approve major decisions beyond PM tolerances; chair or empower the board; escalate to corporate level | Day-to-day task management or detailed scheduling |
| Project steering group / board | Collective governance decisions: continue/stop/change; resolve high-level issues; set priorities | Approve stage/investment decisions, major changes, and strategic direction within remit | Micro-manage team tasks or replace the project manager’s planning role |
| Project manager | Plan, organise, and control delivery to agreed objectives within tolerances | Manage team day-to-day; approve changes and spend within delegated limits; escalate when exceeded | Own the business justification as ultimate account holder |
| Users / user representatives | Define needs, accept outputs against requirements, support adoption | Prioritise user requirements (within process); accept or reject deliverables on fitness for use | Unilaterally change strategic benefits or corporate investment decisions |
| Project team members | Deliver assigned work packages/products to quality and schedule | Technical decisions within their expertise and agreed design authority | Commit the project to new scope or funding outside change control |
| Product owner (iterative contexts) | Represent value for the product; prioritise backlog items against vision and outcomes | Decide order of delivery within agreed product vision and constraints | Replace sponsor accountability for overall investment and strategic alignment |
Terminology note: APM materials use project steering group/board. Treat “project board,” “steering committee,” and “steering group” as the same governance body unless a scenario defines otherwise. The sponsor is often a member or chair of that body but remains a distinct individual accountability for the business case.
Role-by-Role Responsibilities
Users
Users (or those who represent them) understand how the organisation will operate after the project delivers. They contribute requirements, validate that solutions meet needs, participate in testing or reviews, and prepare for transition into business-as-usual. Weak user engagement produces technically complete outputs that fail in adoption — a governance failure as much as a delivery failure, because benefits realisation depends on use.
Project team members
Team members provide specialist skills to create products and complete work packages. They estimate, raise risks and issues, follow agreed processes (quality, configuration, health and safety), and report progress honestly. In matrix structures they may still report to functional managers; governance must clarify which instructions take priority for project-assigned time.
Project manager
The project manager is accountable for managing the project: integrating plans, leading the team, controlling progress against baselines or agile forecasts, applying change control, and communicating status. The PM recommends options but does not, by default, hold unlimited authority to change scope, cost, or benefits. Authority is delegated and bounded.
Project steering group / board
The steering group/board provides collective direction and decision-making above day-to-day management. Typical agenda items: stage-gate go/no-go, major change requests, unresolved escalations, assurance findings, and viability of the business case. Membership often includes the sponsor, senior users, senior suppliers (for supplier-heavy work), and sometimes assurance or finance representation. The board exists so no single operational pressure can quietly rewrite strategy.
Product owner (iterative life cycles)
The product owner is emphasised when delivery is iterative. They own prioritisation of the product backlog, clarify acceptance criteria for backlog items, and maximise value from the team’s capacity within the product vision. They do not replace the sponsor: the sponsor still owns why the organisation is investing and whether the overall initiative remains strategically justified. A common exam trap is assigning investment go/no-go or corporate funding decisions solely to the product owner.
In an iterative project, what is the most appropriate responsibility of the product owner relative to the project steering group?
Why does the APM PMQ syllabus treat the existence of distinct project roles as a governance requirement rather than an administrative preference?