What are the key differences between the 'Scrum Master' and a 'Project Manager'?

All answers to this question.

This is the "Title Swap" trap. A Project Manager is responsible for the "Triple Constraint" (Scope, Schedule, Budget) and "Command and Control." A Scrum Master is a "Servant Leader" responsible for the "Health of the Process." The biggest shift is from "Assigning Tasks" to "Fostering Self-Organization." In Scrum, the team pulls work from the backlog; the SM doesn't push it on them. You focus on removing "Impediments" and coaching the team on Scrum values. Tell your boss that when a team self-assigns, they have higher "Ownership" and "Accountability," which leads to better code quality and faster delivery than when tasks are assigned by a manager.

   Answered 2025-05-20 by Mary Garcia

If the Scrum Master isn't tracking the "Schedule," then who is responsible if the project misses a critical market launch date?

   Answered 2025-05-22 by Paul Walker

• That responsibility lies with the "Product Owner," Paul. The PO manages the "Value" and the "Stakeholders." They use the team's velocity (which the SM helps stabilize) to forecast delivery dates. If a date is at risk, the PO negotiates the "Scope" with the business. The Scrum Master supports this by ensuring the "Sprint Review" is transparent so stakeholders see the progress (or lack thereof) early. It’s a distributed responsibility: the Team delivers the "How," the PO decides the "What" and "When," and the SM ensures the "Process" is enabling both to succeed.

     Commented 2025-05-24 by Richard Hall

I think of it this way: The PM manages the "Plan," but the Scrum Master manages the "Environment" so the plan can actually happen.

   Answered 2025-05-26 by Karen Young

• I agree with Karen. It’s a mindset shift from "Managing People" to "Managing the System." Jessica, stick to your guns on the "No Task Assignment" rule; it’s the core of Scrum!

     Commented 2025-05-28 by Mary Garcia