Are project managers useful in Scrum?
- by Martin Wickman
There are three roles defined in Scrum: Team, Product Owner and Scrum Master. There is no project manager, instead the project manager job is spread across the three roles.
For instance:
The Scrum Master: Responsible for the process. Removes impediments.
The Product Owner: Manages and prioritizes the list of work to be done to maximize ROI. Represents all interested parties (customers, stakeholders).
The Team: Self manage its work by estimating and distributing it among themselves. Responsible for meeting their own commitments.
So in Scrum, there is no longer a single person responsible for project success. There is no command-and-control structure in place. That seems to baffle a lot of people, specifically those not used to agile methods, and of course, PM's.
I'm really interested in this and what your experiences are, as I think this is one of the things that can make or break a Scrum implementation.
Do you agree with Scrum that a project manager is not needed? Do you think such a role is still required? Why?
