“Scrum doesn’t have Project Managers, so we ignore them in our organisation” cover image
Project Management

“Scrum doesn’t have Project Managers, so we ignore them in our organisation”

Explore the evolving role of Project Managers in the Scrum framework.

Willem-Jan Ageling
Apr 24, 2019 • 5 min read
-
Intermediate
Corporate Transformation
Leadership Change
Organizational Change
Scrum Anti Patterns
Stakeholder Engagement Strategies
Show More

Summary

This article discusses the role of Project Managers within the Scrum framework, addressing common misconceptions and exploring the potential need for their presence in organizations using Scrum. It examines how traditional responsibilities are redistributed among Scrum roles and the conditions under which a Project Manager might still be necessary. The piece encourages an understanding of Scrum's flexibility and the importance of integrating non-IT teams into its processes.

Takeaways

  • Integrating non-IT teams into Scrum can enhance transparency and reduce the need for traditional Project Managers.
  • Project Managers are often seen as stakeholders in Scrum, with some traditional tasks absorbed by Scrum roles.
  • Project Managers may still be needed when Scrum Teams depend on external teams or when broader organizational updates are required.
  • Scrum Teams are self-organizing, with the Product Owner managing the backlog and the team setting Sprint Goals.
  • Scrum defines roles as Product Owner, Development Team, and Scrum Master, excluding Project Managers.

Suggested Resources