Overview
Individuals and interactions covers the people side of AgilePM. It starts with agile leadership: leaders set direction and boundaries, then empower teams to decide how to do the work, serve the team by removing obstacles, and lead by example. AgilePM v3 describes this as a shift from project management to project leadership.
The area then covers the roles. At project level, AgilePM keeps distinct business, technical and management perspectives: the Business Sponsor owns the business case and funding, the Business Visionary holds the business vision, the Technical Coordinator is the technical authority, and the Project Manager coordinates at project level with a facilitative style. At delivery level, Scrum Teams with a Product Owner, Scrum Master and Developers build the solution. The third topic is how these people, and wider stakeholders, work together so that business direction reaches the team quickly and decisions are taken at the right level.
How it's tested
Expect who-does-what and which-leadership-style questions. You are given a responsibility or a situation and choose the role accountable for it, or the leadership behaviour AgilePM expects. Distractors give a real responsibility to a plausible but wrong role, or describe directive management where AgilePM expects facilitation and empowerment.
-
Match responsibility to role
A responsibility such as owning the business case or the technical architecture is given and you choose the role accountable for it.
-
Leadership behaviour
A leader faces a situation and you choose the response that empowers and serves the team rather than directing it.
-
Interaction and escalation
A question asks how the Product Owner, Scrum Master, team and project roles work together or where an issue should go.
A question asks who should decide whether the project still makes business sense after a large cost increase. The Project Manager is tempting because they track the budget, and the Product Owner because they order the backlog. But continued business justification and funding belong to the Business Sponsor, the most senior business role, so that is the answer. Ask who owns the business case, not who noticed the problem.
Syllabus topics 3
Official syllabus topics from the APMG International outline, in outline order.
4.1 Agile leadership principles and behavioursServant leadership, empowerment within boundaries, and leading by example.
- What it means
- Agile leaders set a clear vision and boundaries, trust and empower people to decide how to achieve the goals, remove obstacles, encourage open communication and learning, and model the behaviours they expect. AgilePM v3 frames this as project leadership rather than task management.
- What to understand
- Empowerment works within agreed boundaries, often called tolerances: the team decides inside them and escalates only when they would be exceeded. Leadership behaviours such as listening, coaching and making it safe to raise problems are what make self-organisation work.
- How it shows up
- A leader is tempted to take over a team decision and you choose the response that sets direction and support without micromanaging.
- Common confusion
- Equating empowerment with no leadership; leaders still set direction, boundaries and priorities.
4.2 AgilePM roles, responsibilities and key relationshipsBusiness, technical and management roles at project level, and what each owns.
- What it means
- The Business Sponsor is the most senior business role, owning the business case and budget. The Business Visionary owns the business vision and makes sure the solution delivers the intended business change. The Technical Coordinator is the technical authority for architecture and standards. The Project Manager coordinates at project level, facilitates and manages by exception.
- What to understand
- Roles are responsibilities, not job titles: one person can hold more than one role on a small project, but the business, technical and management perspectives must each be covered. The Project Manager plans and coordinates at project level and leaves detailed task planning to delivery teams.
- How it shows up
- A decision or responsibility is described and you pick the role that owns it, or spot a role acting outside its responsibilities.
- Common confusion
- Giving business decisions, such as continued funding, to the Project Manager instead of the Business Sponsor.
4.3 How stakeholders, Product Owner, Scrum Master and team collaborateLinking project-level roles and stakeholders to Scrum Teams.
- What it means
- The Product Owner represents business priorities to a delivery team and orders its backlog, working with the business roles above and stakeholders around the project. The Scrum Master helps the team and the organisation use Scrum effectively and removes impediments. Developers build the solution and stakeholders give feedback, especially at Sprint Reviews.
- What to understand
- Business direction flows from sponsor and visionary through the Product Owner to the backlog, and feedback flows back through reviews and demonstrations. Issues beyond a team's authority are escalated through the project roles rather than resolved by bypassing them.
- How it shows up
- A stakeholder wants to change priorities or add work, and you choose the correct channel or the role that should engage them.
- Common confusion
- Letting stakeholders give work directly to Developers, bypassing the Product Owner and the backlog.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Servant leadership
A leadership approach in which the leader's main job is to enable others, by removing obstacles, coaching and creating the conditions for the team to succeed.
- Remember
- The leader serves the team's effectiveness rather than directing each task.
- Tested as
- Leadership-style questions and Scrum Master questions.
- Trap
- Choosing an answer where the leader solves the team's problem for them without involving them.
-
Empowerment within boundaries
Teams are trusted to make decisions about their work within agreed limits on time, cost, scope and quality, and escalate only when those limits would be breached.
- Remember
- Empowered does not mean unlimited; boundaries and escalation are part of it.
- Tested as
- Questions on who decides and when to escalate.
- Trap
- Escalating every decision, or never escalating anything.
-
Project leadership vs. project management
AgilePM v3 shifts emphasis from managing tasks and plans to leading people toward value, setting direction and supporting decision-making.
- Remember
- One of APMG's five headline v3 changes.
- Tested as
- Questions on the Project Manager's style.
- Trap
- Picking a command-and-control response because it sounds decisive.
-
Business Sponsor
The most senior business role on the project, accountable for the business case, the budget and the project's continued business justification.
- Remember
- Funding and go or no-go business decisions sit here.
- Tested as
- Who-owns-it questions about the business case and budget.
- Trap
- Assigning these decisions to the Project Manager.
-
Business Visionary
A senior business role that owns the vision of the business change and makes sure the solution delivers it, interpreting the sponsor's needs for the project.
- Remember
- Vision and business direction, below the sponsor and above day-to-day backlog work.
- Tested as
- Role-matching questions.
- Trap
- Confusing the visionary's strategic direction with the Product Owner's backlog ordering.
-
Technical Coordinator
The project's technical authority, responsible for the technical design and architecture, standards and making sure the solution's parts fit together.
- Remember
- Technical counterpart to the Business Visionary.
- Tested as
- Questions about architecture or technical standards.
- Trap
- Giving architecture decisions to the Project Manager.
-
Project Manager (AgilePM style)
Coordinates all aspects of the project at a high level, works facilitatively, and manages delivery teams by agreeing objectives and tolerances rather than assigning tasks.
- Remember
- Plans at project level; teams plan their own detailed work.
- Tested as
- Leadership and planning questions.
- Trap
- Choosing the Project Manager to allocate daily tasks.
-
Product Owner in an AgilePM project
Represents business priorities to a Scrum Team and is accountable for ordering its backlog, working with the project's business roles and stakeholders.
- Remember
- One person per backlog; stakeholders influence the work through the Product Owner.
- Tested as
- Interaction and channel questions.
- Trap
- Letting a stakeholder give work straight to a Developer.
-
Scrum Master in an AgilePM project
Helps the team and organisation use Scrum effectively, coaches, facilitates events on request and removes impediments.
- Remember
- Not the team's manager and not the project manager.
- Tested as
- Who-does-what questions.
- Trap
- Equating the Scrum Master with the Project Manager.
-
Roles vs. people
A role is a set of responsibilities; on small projects one person may hold several roles, and on large ones a role may be shared across people.
- Remember
- Every perspective must be covered, whatever the staffing.
- Tested as
- Questions about small projects combining roles.
- Trap
- Thinking every role needs a separate full-time person.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Business Sponsor vs. Business Visionary vs. Product Owner
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Business Sponsor | Most senior business role, owns business case and budget | Decides whether the project remains justified and funded | Treating them as a day-to-day decision-maker on features |
| Business Visionary | Owns the vision of the business change | Sets business direction for the solution | Confusing direction-setting with backlog ordering |
| Product Owner | Represents business priorities to a Scrum Team | Orders the backlog the team works from | Giving them the funding decision |
Project Manager vs. Scrum Master
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Project Manager | Coordinates the project at a high level | Project-level planning, tolerances and governance reporting | Allocating daily tasks to Developers |
| Scrum Master | Enables a team's effective use of Scrum | Team-level coaching and removing impediments | Acting as the team's line manager |
Directive management vs. agile leadership
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Directive management | Manager plans and assigns tasks and checks completion | Decisions concentrated at the top | Choosing it because it sounds decisive |
| Agile leadership | Leader sets vision and boundaries and enables the team | Decisions taken at the lowest sensible level | Reading it as no leadership at all |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Project Manager owns the business case
- What candidates pick
- The Project Manager decides whether the project should continue after costs rise.
- Why it looks right
- The Project Manager monitors the budget and reports the problem.
- Why it's wrong
- Continued business justification and funding belong to the Business Sponsor; the Project Manager escalates.
Clue to watch for The decision concerns whether the project is still worth funding.
-
Manager allocates daily tasks
- What candidates pick
- The Project Manager assigns tasks each morning to keep the team busy.
- Why it looks right
- It looks efficient and in control.
- Why it's wrong
- AgilePM teams plan and manage their own detailed work; the Project Manager leads at project level.
Clue to watch for A question about how detailed work is assigned.
-
Stakeholder goes straight to a Developer
- What candidates pick
- Allow a senior stakeholder to ask a Developer directly for an extra feature.
- Why it looks right
- The stakeholder is senior and the request seems small.
- Why it's wrong
- New work goes through the Product Owner and the backlog so it can be prioritised against everything else.
Clue to watch for Work arriving outside the backlog.
-
Empowerment without limits
- What candidates pick
- The team decides to extend the project deadline because it is empowered.
- Why it looks right
- Empowerment sounds like full authority.
- Why it's wrong
- Empowerment applies within agreed tolerances; breaching them is escalated to the right role.
Clue to watch for A decision that would change project-level time, cost or scope.
-
Visionary and Product Owner are the same
- What candidates pick
- The Business Visionary orders each team's backlog item by item.
- Why it looks right
- Both roles carry business direction.
- Why it's wrong
- The visionary sets the business vision for the change; detailed backlog ordering for a team is the Product Owner's accountability.
Clue to watch for The task is detailed, team-level backlog ordering.
-
Every role needs a different person
- What candidates pick
- A small project must recruit a separate person for each AgilePM role.
- Why it looks right
- Role lists look like organisation charts.
- Why it's wrong
- Roles are responsibilities; one person can hold several on a small project as long as each perspective is covered.
Clue to watch for A small project with limited staff.
Answer framework
Use these steps for any question about who decides, who acts or how a leader should behave.
- Classify the decision: business justification and funding, business direction, technical design, project coordination, backlog order, or team-level work.
- Map it to the owning role: Business Sponsor, Business Visionary, Technical Coordinator, Project Manager, Product Owner, or the Developers.
- Check boundaries: if the decision stays within the team's agreed tolerances the team decides; if it breaches them, escalate to the next level.
- For leadership questions, prefer the response that sets direction, coaches and removes obstacles over one that takes the decision away from the team.
- Confirm the channel: requests and changes reach the team through the Product Owner and backlog, not directly from stakeholders to Developers.
Practice question
Want more like this? The AgilePM Foundation practice test has questions for every domain.
Checklist
0 of 11
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Build a one-page role map before anything else. Draw three layers: business direction (Business Sponsor, Business Visionary), project coordination and technical authority (Project Manager, Technical Coordinator), and delivery (Product Owner, Scrum Master, Developers). For each role, write the one decision it owns and the one thing it must not do.
Then study leadership. Write three short scenarios in which a leader is tempted to take over: a slow decision, a conflict, a missed estimate. For each, write the agile leadership response that sets direction and supports the team. This prepares you for the behaviour questions, where the directive option is usually the trap.
The underestimated topic is how project roles and Scrum roles connect. Practise tracing a stakeholder request and a business-case problem through the roles so you know who receives each and who decides.
Afterwards, move to collaboration and communication, which builds on these relationships, then governance, where the sponsor's role returns. Finish with a short practice set of who-does-what questions and review every miss by asking which role actually owns that decision.
FAQ
Who owns the business case on an AgilePM project?
The Business Sponsor, the most senior business role, who is accountable for the business case, the budget and the project's continued justification.
Is the Project Manager the same as the Scrum Master?
No. The Project Manager coordinates the whole project and reports to governance, while a Scrum Master helps one team use Scrum effectively. They work at different levels.
Does the Project Manager assign tasks to Developers?
No. Delivery teams plan and organise their own detailed work. The Project Manager agrees objectives and tolerances and leads at project level.
Can one person hold several AgilePM roles?
Yes, especially on small projects. Roles are sets of responsibilities, and the requirement is that the business, technical and management perspectives are all covered.
How does the Product Owner relate to the business roles?
The Product Owner turns business direction from the project's business roles and stakeholders into an ordered backlog for the team, and brings feedback back from reviews.
What changed about leadership in AgilePM v3?
APMG describes a shift from project management to project leadership, emphasising setting direction, enabling teams and supporting decisions over controlling tasks.
How many questions cover roles and leadership?
APMG publishes no per-area counts. An even split suggests about five of the 50 questions, but role knowledge also helps in collaboration, planning and governance questions.
Other Project Management certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- PRINCE2 7 Practitioner Study guide
- PMI Risk Management Professional Study guide
- PMI Scheduling Professional Study guide
- Project Management Professional Study guide
- CompTIA Project+ Study guide
- PRINCE2 7 Foundation Study guide
- Portfolio Management Professional Study guide
- Program Management Professional Study guide
- Certified Associate in Project Management Study guide
- PMI Agile Certified Practitioner Study guide
- Project Management Professional (PMBOK 7) Study guide
- Disciplined Agile Scrum Master Study guide
Test your Domain 4 knowledge
You have covered agile leadership, the AgilePM project roles and how they work with the Product Owner, Scrum Master and team. Check that you can match each decision to the role that owns it.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the AgilePM Foundation AI tutor Get any concept explained your way