Define roles, responsibilities and relationships
Why everyone needs to know who decides what, the three interests every project must represent, and why relationships matter as much as structure.
Scene 1
Define roles, responsibilities and relationships
Why everyone needs to know who decides what, the three interests every project must represent, and why relationships matter as much as structure.
Caption 1 of 3
Explain why a project needs an agreed structure of roles and responsibilities
Read all scene text
- Explain why a project needs an agreed structure of roles and responsibilities
- Name the three project interests: business, user and supplier
- Explain why relationships were added to this principle in the 7th edition
Scenes animate with GSAP. Use pause or replay at any time.
In this session
- Explain why a project needs an agreed structure of roles and responsibilities
- Name the three project interests: business, user and supplier
- Explain why relationships were added to this principle in the 7th edition
It's time to sort out who does what.
Let's say it's week 5. Priya, your head baker, pops into the York shop and asks the builder for a bigger oven. The builder says "no problem" and adds £3,000 to the bill. Sam only hears about it a week later.
What went wrong?
Select the arrow to learn more
1 of 4
Priya's view
Priya will be the one using the kitchen every day, so Priya assumed it was their call to make.
Three interests around the table
Every project serves three groups, and all three need a voice when decisions are made:
- Business: is it worth the money? At Fern & Flour, that's you, the person investing.
- User: will it work for the people who'll use it? That's Priya and the bakers and counter staff who'll work in York.
- Supplier: can it be built, and how? That's your builder and the shopfitter.
Roles, not job titles
PRINCE2 talks about roles, not jobs. A role is a set of responsibilities on the project. Priya's job is head baker, but on the York project Priya's role is to represent the users.
On a small project, one person can hold more than one role. On a large one, a role might be shared between several people. What matters is that every responsibility has an owner, and everyone knows who that owner is.
Why relationships matter
In the 7th edition, this principle gained a new word: relationships. A neat chart of roles isn't enough if the people in it don't talk, trust each other or sort out disagreements.
Relationships also reach beyond the project team. Your landlord, the council's planning officer, your neighbours on the street and your Leeds regulars are all stakeholders. Knowing how you'll work with each of them is part of defining the project's structure.
So who should have decided about the oven?
With clear roles, the oven request would go like this: Priya raises it with Sam. Sam works out what it would do to cost, time and the business case. Then the person or group with authority for changes of that size makes the decision. The builder only starts once it's approved.
You'll see exactly how that works in the issues practice. For now, the point is simple: the answer to "who decides?" should never be a surprise.
Key points to remember
- A project needs an agreed structure of accountability and responsibility.
- The business, user and supplier interests must all be represented in decisions.
- PRINCE2 uses roles, not job titles. One person can hold more than one role.
- The 7th edition adds relationships: people and stakeholders must work well together.
Knowledge check
Choose one answer
Principles
Priya will work in the York kitchen every day. Which project interest does Priya represent?
Sign in to save your result. Knowledge checks can be retried any time.
PRINCE2® is a registered trademark of the PeopleCert group. MockAcademy is independent and not affiliated with, endorsed by or licensed by PeopleCert.