Scrum Master vs. Project Manager: How do they direct teams?
This tests your understanding of servant-leadership vs. command-and-control. A good answer contrasts their core goals (process vs. project), team interaction (coaching vs. directing), and how they handle change. Red flag: saying an SM is just an 'agile PM.'
What's really being asked
This question tests your understanding of the fundamental philosophical difference between traditional project management and agile frameworks. The interviewer is looking for evidence that you've worked in a true agile environment and grasp the shift from "command and control" (Project Manager) to "servant leadership" (Scrum Master). They want to see if you can articulate how this difference manifests in day-to-day interactions with the development team.
The full answer
A strong answer contrasts the roles across four key areas. First, core philosophy: a PM manages the "iron triangle" (scope, cost, time) to ensure project delivery, while an SM coaches the team on the Scrum framework to maximize the value they create. Second, team interaction: a PM directs the team, assigns tasks, and tracks individual progress. An SM facilitates, coaches the team to be self-organizing, and removes impediments, but never assigns work. The team pulls work from the backlog. Third, authority and responsibility: a PM has authority over the project plan and is accountable for its success. An SM has authority over the process, but the team is accountable for the work and the Product Owner is accountable for the product. Fourth, handling change: a PM manages change through formal control processes to minimize deviation from the plan. An SM embraces change and coaches the team and PO on how to adapt the backlog.
The mistakes people make
A major red flag is saying, "A Scrum Master is just an agile Project Manager." This shows a fundamental misunderstanding. Another common mistake is describing a Scrum Master who acts like a project coordinator—running stand-ups as status reports, tracking individual tasks, and reporting progress to management. This describes a "Scrum-but" anti-pattern, not a functional Scrum Master. Weak answers focus only on ceremonies ("the SM runs standup") without explaining the underlying purpose (facilitating team communication, not reporting to a manager).
What usually comes next
"Describe a time a stakeholder tried to bypass the Product Owner and give your team work directly. How did you (or the Scrum Master) handle it?" "Can one person fulfill both the PM and SM role on a project?" (The correct answer is no, due to inherent conflicts of interest between protecting the team/process and delivering a fixed scope/schedule). "What metrics would a good SM track vs. a good PM?"
A concrete example
Scenario: A VP demands a new, "urgent" feature be added mid-sprint. A traditional PM would assess the impact on the timeline and budget, get approval for the change order, update the Gantt chart, and then assign the new tasks to specific developers, potentially re-prioritizing their existing work. A Scrum Master would shield the team from the VP's direct request. They would explain to the VP that the sprint commitment is fixed to protect the sprint goal. They would then coach the Product Owner on how to discuss the new item with the VP and where it might fit in a future sprint's priority. The SM facilitates communication but protects the team's focus and the integrity of the sprint.
Interview question
Which statement best characterizes the fundamental difference in how a Scrum Master and a Project Manager interact with a development team?
- a.A Scrum Master reports individual team member performance to stakeholders, whereas a Project Manager protects the team from external interruptions.
- b.A Scrum Master assigns specific tasks to team members, whereas a Project Manager focuses on facilitating team collaboration.
- c.A Scrum Master coaches the team to be self-organizing and removes impediments, while a Project Manager directs tasks and tracks individual progress.Correct
- d.A Scrum Master ensures the project adheres to the initial scope and budget, while a Project Manager guides the team on agile principles.
Why? this is the answer
The Scrum Master's role is to coach the team towards self-organization and remove obstacles, never assigning tasks. In contrast, a Project Manager typically directs tasks and monitors individual progress to ensure project delivery, making option C correct. Option B is incorrect as assigning tasks is a PM function, not an SM function.
Just read this? Test yourself on what you have been reading.
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles