Study guide
3.6 Why Scrum Has No Project Manager
Certified ScrumMaster CSM
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Agile Foundations, Scrum Theory & Empirical Process Control
1.1 Agile Manifesto & Lean Thinking 1.2 Empirical Process Control 1.3 Complex Adaptive Systems & Cynefin Framework 1.4 Scrum Framework Overview & Core Rules 1.5 Iterative & Incremental Delivery 1.6 Partial Scrum Adoption & Its Consequences
2 Chapter 2: The Five Scrum Values & Cultural Mindset
2.1 Commitment & Focus 2.2 Openness & Respect 2.3 Courage & Ethical Leadership
3 Chapter 3: Scrum Team Accountabilities & Dynamics
3.1 Developers Accountability & Self-Management 3.2 Product Owner Accountability & Business Value 3.3 Scrum Master Accountability & Servant Leadership 3.4 Team Characteristics, Size & Cross-Functionality 3.5 How the Scrum Team Interacts Across a Sprint 3.6 Why Scrum Has No Project Manager
4 Chapter 4: The Five Scrum Events & Timeboxing
4.1 The Sprint Container & Goal Preservation 4.2 Sprint Planning Event 4.3 Daily Scrum Event & Micro-Planning 4.4 The Sprint Review 4.5 The Sprint Retrospective 4.6 Effects of Skipping the Sprint Retrospective 4.7 Choosing a Suitable Sprint Length 4.8 Inspect & Adapt at Every Scrum Event
5 Chapter 5: Scrum Artifacts, Commitments & Definition of Done
5.1 Product Backlog & Product Goal 5.2 Sprint Backlog & Sprint Goal 5.3 Increment & Definition of Done 5.4 Multi-Team DoD & Technical Debt Management 5.5 Product Backlog Refinement 5.6 Product Backlog Item Attributes & Ordering 5.7 Creating & Evolving the Definition of Done
6 Chapter 6: Scrum Master Core Competencies, Servant Leadership & Coaching
6.1 Facilitation & Professional Coaching Techniques 6.2 Removing Impediments & Root Cause Analysis 6.3 Servant Leadership & Organizational Change 6.4 Agile Metrics, Velocity Traps & Scaling Basics 6.5 Development Practices That Protect the Increment 6.6 Serving the Product Owner 6.7 Organizational Design Change from Adopting Scrum
7 Chapter 7: The CSM Test — Format, Logistics & Official Blueprint
7.1 CSM Test Format & Scoring 7.2 Course Prerequisite, Attempts & Renewal 7.3 The Official Learning Objectives Blueprint
3.6 Why Scrum Has No Project Manager
Key Takeaways Explain This Topic AI
CSM Learning Objective 3.9 asks candidates to discuss why Scrum does not have a project manager — the answer is that the accountability was distributed, not deleted.
Scope and priority decisions moved to the Product Owner; how and how-much decisions moved to the self-managing Developers; process effectiveness and impediment removal moved to the Scrum Master.
Scrum manages products continuously rather than projects with a defined end, so a temporary, plan-driven coordinating role no longer fits the structure.
A person may keep the job title 'project manager' in an organization; what cannot exist is a fourth accountability inside the Scrum Team that assigns work or owns the plan.
The Scrum Master is not a renamed project manager: they have no authority over scope, budget, staffing, or task assignment.
Last updated: August 2026
Quick Answer: Scrum has no project manager because the work that role performed was distributed across the three accountabilities , not abolished. The Product Owner took value, scope ordering, and stakeholder direction. The Developers took estimation, planning, and task allocation through self-management. The Scrum Master took process effectiveness and impediment removal. Nothing was left over to justify a fourth accountability inside the team.
CSM Learning Objective 3.9 asks you to discuss why scrum does not have a project manager . The examinable answer is structural, not ideological — and candidates who answer "because Agile doesn't believe in managers" lose the mark.
Where the Responsibilities Actually Went
Traditional Project Manager Responsibility Where It Lives in Scrum Why It Moved There
Defining and prioritizing scope Product Owner Value decisions need a single accountable person the organization respects, close to stakeholders
Committing to a delivery date and scope Nobody — replaced by empiricism In complex work, forecasts come from observed Increments, not up-front commitment
Estimating effort Developers The Scrum Guide: "The Developers who will be doing the work are responsible for the sizing"
Allocating tasks to individuals Developers, through self-management The team internally decides who does what, when, and how
Producing the plan for the work Developers The Sprint Backlog is "a plan by and for the Developers"
Status reporting to management The artifacts themselves Transparency replaces reporting; the Increment and backlogs are the status
Escalating and removing blockers Scrum Master Causing the removal of impediments is an explicit Scrum Master accountability
Managing process and team effectiveness Scrum Master The Scrum Master is accountable for the Scrum Team's effectiveness
Quality assurance sign-off Definition of Done Quality becomes a standard the Developers conform to, not a gate a manager approves
Read down that middle column and the argument makes itself: every responsibility landed somewhere with a clear accountability. A project manager inside the Scrum Team would necessarily take one of them back — and each one, taken back, breaks something specific.
The Two Deeper Reasons
1. Scrum manages products, not projects. A project is temporary and ends; a product is ongoing. Scrum's structure reflects this — the Product Goal is "the long-term objective for the Scrum Team," and a new Sprint starts immediately after the previous one concludes. There is no closure phase, so there is no need for a role whose remit is to shepherd a temporary endeavour from initiation to closure.
2. Self-management is not compatible with external task assignment. The Scrum Guide defines self-managing as the team "internally deciding who does what, when, and how," and says of Sprint Planning Topic Three: "No one else tells them how to turn Product Backlog items into Increments of value." A project manager who assigns tasks does not merely add overhead — they remove the property that makes the Developers able to adapt daily toward the Sprint Goal.
The Trap: "The Scrum Master Is Just a Project Manager"
This is the most frequently tested confusion in the entire accountability topic.
- Dimension Traditional Project Manager Scrum Master
- Authority over scope Yes — manages scope against a baseline None — scope belongs to the Product Owner
- Authority over people Often line-manages or assigns tasks None — Developers self-manage
- Authority over budget Typically yes None
- Primary output Plans, schedules, status reports An effective team and an environment where Scrum works
- Mode of influence Positional authority Leadership through teaching, coaching, facilitation, and influence
- Accountable for Delivering to plan Establishing Scrum and the Scrum Team's effectiveness
The Scrum Master is described as a "true leader who serves the Scrum Team and the larger organization." Leadership without positional authority is the defining constraint, and it is the opposite of the project manager's core instrument.
What This Does Not Mean
Be careful with absolutes — the exam punishes them in both directions.
Scrum does not forbid the job title of project manager from existing in an organization. Many people with that title work productively alongside Scrum Teams on procurement, vendor contracts, portfolio funding, or regulatory milestones.
Scrum does not claim projects never exist. The Scrum Guide itself notes that "each Sprint may be considered a short project."
What Scrum defines is that there are exactly three accountabilities within the Scrum Team . A fourth one that owns the plan or assigns the work is not part of the framework.
Real-World CSM Scenario
An organization adopting Scrum asks its experienced project managers to become Scrum Masters, and one of them begins maintaining a task-assignment spreadsheet, running the Daily Scrum by calling on each Developer in turn, and reporting individual completion percentages to a steering group.
Every one of those three behaviours contradicts a specific Scrum rule: task assignment contradicts self-management, running the Daily Scrum as a round contradicts an event held by and for the Developers, and individual-level reporting contradicts team-level transparency through artifacts. The coaching move is not to tell the person they are "doing it wrong" but to redirect their real strengths — stakeholder navigation, dependency management, organizational escalation — toward removing the organizational impediments the team cannot reach, which is exactly what the Scrum Master accountability calls for.