Skip to content
Tutorials Center
My learning

Topics

Lesson 4 of 41 ยท Getting Started

Project Team Roles and Responsibilities

Learn the main project roles: sponsor, project manager, team members, product owner, business analyst and more. Build a RACI matrix and avoid unclear ownership.

A project succeeds or fails through people, and people work best when they know what they own. Unclear roles produce two classic problems: tasks nobody does because everyone assumed someone else would, and tasks done twice by two people who each thought it was theirs.

This lesson lists the roles found on most projects, explains how they differ between traditional and agile teams, and shows how a RACI matrix makes ownership explicit.

Roles on a typical project

Role Main responsibility
Sponsor Funds the project, owns the business case, removes high-level obstacles, makes final decisions on scope and budget
Customer / client The person or group who receives and accepts the result
Steering committee Senior stakeholders who guide direction and approve major changes
Project manager Plans, coordinates, controls and reports (see the project manager's role)
Business analyst Gathers and documents requirements, bridges business and technical teams
Team members Do the technical or functional work: design, development, test, operations
Subject-matter experts Provide specialist advice on request
Quality assurance Plans and carries out checks so the result meets standards
Vendors and suppliers Provide outside goods or services under contract
End users Use the result; their feedback shapes requirements and acceptance

A person can hold several roles on a small project, and one role can be shared. What matters is that every responsibility has a clear owner.

Software team roles

A software project adds specialist roles: solution architect, UI/UX designer, front-end and back-end developers, database specialist, test engineer, DevOps or release engineer, and technical writer. In agile teams the vocabulary changes.

  • Product owner: decides what is built and in what order; owns the backlog.
  • Scrum master: coaches the team on the process and removes impediments (not a boss).
  • Development team: a self-organizing, cross-functional group that delivers the increment.

See the later chapter on Agile and Scrum for details on how these differ from traditional roles; the key idea is that agile spreads some project manager duties across the three roles.

Who does what?

Sponsor Pays and decides
Project manager Plans and coordinates
Team Builds the result
Users Accept and use it

Four groups cover most projects.

1 / 2

Responsibility, authority and accountability

Three ideas are worth separating.

  • Responsibility: doing the work.
  • Accountability: answering for the result; there can be only one accountable owner per item.
  • Authority: the right to make decisions and commit resources.

Trouble starts when someone is held accountable without the authority to decide.

The RACI matrix

A RACI matrix assigns each activity or deliverable one of four codes to each person or role.

  • R: Responsible: does the work. There may be several.
  • A: Accountable: signs off and owns the outcome. Exactly one per item.
  • C: Consulted: gives input before the decision or work (two-way).
  • I: Informed: told about progress or outcome (one-way).
Deliverable Sponsor PM Analyst Developer QA
Business case A R C I I
Requirements C A R C I
Build feature I A C R C
Test plan I A C C R
Go-live decision A R I C C

Rules for a healthy matrix: every row has exactly one A, at least one R, and nobody is flooded with R's.

Python Validate a RACI matrix

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The last row is deliberately broken: two "A"s mean nobody is truly accountable. Fix it by changing the PM to R.

Workload by person

Python Count responsibilities per person

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Building a good team

  • Pick people for skills, but also for how they work together.
  • Clarify roles in a kickoff meeting and write them down.
  • Keep a team charter: working hours, tools, how decisions are made, how conflict is handled.
  • Mind the stages every team passes: forming, storming, norming, performing, adjourning. Storming is normal; plan for it.
  • Release people properly at the end and recognise their work.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. In a RACI matrix, how many people should be Accountable for one deliverable?

    A single accountable owner prevents the diffusion of responsibility.
  2. 2. Who funds the project and owns the business case?

    The sponsor provides funding and owns the business case.
  3. 3. What does 'Consulted' mean in RACI?

    Consulted people are asked for input before a decision or work is done.
  4. 4. In Scrum, who decides the order of the work in the backlog?

    The product owner owns and orders the product backlog.

Summary

  • Typical roles: sponsor, project manager, analyst, team members, QA, vendors and users.
  • Agile teams use product owner, scrum master and development team.
  • Responsibility, accountability and authority are different things.
  • A RACI matrix gives every deliverable one accountable owner and clear responsibilities.

Next: Projects, Programs and Portfolios