Scrum Master vs. Project Manager: How do they direct teams?

WHAT THIS TESTS: 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.

A GOOD ANSWER COVERS: 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.

COMMON WRONG ANSWERS: 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).

LIKELY FOLLOW-UPS: "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?"

ONE 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.