2.3. Project Roles and Responsibilities
💡 First Principle: A project manager and a project sponsor both care about the project succeeding, but they operate at different altitudes. The sponsor authorizes and champions the project from outside day-to-day execution; the project manager runs it from inside. Confusing "who has authority to approve a budget change" (usually the sponsor) with "who manages the team doing the work" (the PM) is a recurring exam pattern.
PM vs. sponsor, and team vs. sponsor. The project sponsor provides resources, removes organizational obstacles, and champions the project at a strategic level — often approving major changes or funding. The project manager plans, coordinates, and directs day-to-day execution. The project team does the hands-on work. A scenario asking "who should escalate this budget overrun for approval?" is usually pointing at the sponsor; "who should resolve this task-sequencing conflict between two team members?" is usually pointing at the PM.
The many hats of a project manager. PMI explicitly calls out several roles a PM plays depending on the moment: initiator (getting the project started), negotiator (resolving competing interests), listener (understanding stakeholder concerns before acting), coach (developing team members), working member (contributing hands-on effort, not just directing), and facilitator (enabling the team's own decision-making rather than dictating it). Scenario questions describe a specific behavior and ask which role it demonstrates.
| Behavior in the Scenario | Role Being Demonstrated |
|---|---|
| Running a retrospective and letting the team surface its own solutions | Facilitator |
| Mediating between two stakeholders who want conflicting priorities | Negotiator |
| Spending an afternoon helping a struggling team member build a new skill | Coach |
| Personally writing part of the deliverable alongside the team | Working member |
Leadership vs. management. Management is the set of planning, organizing, and controlling processes applied to resources and objectives — it's largely about process and structure. Leadership is inspiring, motivating, and guiding people toward a shared vision — it's largely about people and direction. A PM needs both, but a scenario that describes "setting a budget and tracking spend against it" demonstrates management; one that describes "rallying a discouraged team around the project's purpose after a setback" demonstrates leadership.
⚠️ Exam Trap: Don't assume "leadership" only belongs to senior titles and "management" only belongs to PMs. The exam tests recognizing the behavior, not the job title attached to it — a team member can demonstrate leadership, and a PM can be, in a given moment, purely executing management tasks.
Emotional intelligence (EQ). EQ is the ability to recognize, understand, and manage your own emotions and those of others. On a project team, high EQ shows up as reading a stakeholder's frustration accurately before responding, or recognizing when a team member's quietness signals a real problem rather than simple focus. The exam frames EQ as directly impacting project outcomes — poor EQ leads to missed conflict signals and escalations that better awareness would have caught earlier.
Why this whole subsection is really one skill wearing different hats. Sponsor-vs-PM, situational roles, leadership-vs-management, and EQ can look like four separate topics to memorize, but they're testing the same underlying judgment from four angles: correctly reading what a moment calls for and responding at the right altitude. A PM who applies "coach" energy when the moment calls for "negotiator," or leans on management process when the team actually needs leadership, is making the same category of mistake each time — matching the wrong tool to the situation. Scenario questions in this domain are rarely testing whether you know the definitions; they're testing whether you can diagnose the moment correctly and respond with the behavior it actually calls for.
