A Study of the Scrum Master's Role
John Noll, Mohammad Abdur Razzak, Julian M Bass, and Sarah Beecham

TL;DR
This study explores the Scrum Master's role in agile development, identifying key activities and roles, and highlights the overlap with project management that may impact team performance.
Contribution
It provides a detailed analysis of Scrum Master activities and reveals their dual role as Project Managers, suggesting a need to re-evaluate organizational roles in Scrum adoption.
Findings
Nine core activities performed by Scrum Masters
Scrum Masters often also act as Project Managers
Potential conflicts arising from dual roles
Abstract
Scrum is an increasingly common approach to software development adopted by organizations around the world. However, as organizations transition from traditional plan-driven development to agile development with Scrum, the question arises as to which Scrum role (Product Owner, Scrum Master, or Scrum Team Member) corresponds to a Project Manager, or conversely which Scrum role should the Project Managers adopt? In an attempt to answer this question, we adopted a mixed-method research approach comprising a systematic literature review and embedded case study of a commercial software development team. Our research has identified activities that comprise the Scrum Master role, and which additional roles are actually performed by Scrum Masters in practice. We found nine activities that are performed by Scrum Masters. In addition, we found that Scrum Masters also perform other roles, most…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
