Are Scrum Masters the new Project Managers?
Yesterday I registered for a website, and the drop down list for job titles had entries for ‘Project Manager/Scrum Master’ and ‘Developer/Engineer’. I was in a bit of a dilemma there. I am currently Scrum Master AND developer on my team. I never really considered Scrum Master being a job title, so I picked developer. Problem solved, right? But wait, ‘Project Manager/Scrum Master’?! Are they the same? Same category at least? Is a Scrum Master a lightweight Project Manager? — I think: No, possibly and sort of.
Project Manager (PM)
The PMI Project Management Body of Knowledge recognizes five basic process groups and nine knowledge areas being typical of almost all projects. These are the domains of a Project Manager. The five basic process groups identified are
- Initiating,
- Planning,
- Executing,
- Monitoring and Controlling and
- Closing.
Some or all of these processes are contained in each of the nine knowledge areas consisting of
- Integration,
- Scope,
- Time,
- Cost,
- Quality,
- Human Resource,
- Communications,
- Risk and
- Procurement.
Scrum Master (SM)
The Scrum Guide defines the Scrum Master role as follows:
“The ScrumMaster is responsible for ensuring that the Scrum Team adheres to Scrum values, practices, and rules. The ScrumMaster helps the Scrum Team and the organization adopt Scrum. The ScrumMaster teaches the Scrum Team by coaching and by leading it to be more productive and produce higher quality products. The ScrumMaster helps the Scrum Team understand and use self-management and cross-functionality. However, the ScrumMaster does not manage the Scrum Team; the Scrum Team is self-organizing.” [emphasis is mine]
Comparison
Both SMs and PMs try to create an environment that enables the team to do their work. They are facilitators. However, they are doing this in completely different ways. SMs manage the development process and remove obstacles identified by the team, whereas traditional PMs manage resources (including the team members) and do all of the planning, monitoring and controlling involved.
For Scrum teams, the project planning consists of
- the Product Backlog,
- the Release Backlog (both owned by the Product Owner) and
- the Sprint Backlog (picked and estimated during the Sprint Planning Meeting by the development team) together with
- the corresponding Release and Sprint Burndown Charts (kept up do date by the SM).
The SM monitors the team’s achievements during the sprint using the Sprint Burndown Chart and raises discrepancies to the Product Owner, who then controls the outcome of the sprint by adjusting its scope. The development team also monitors and controls its own progress daily during the Daily Scrums. In Scrum terms this is known as inspect and adapt. This means the PM tasks of planning, monitoring and controlling, are shared by the SM, the Product Owner and the development team.
A traditional PM would do all these tasks by himself after gathering the status from the team in regular meetings. This also means that he is held ultimately accountable for the success or failure of the entire project.
Conclusion
And so, I would answer the question, if Scrum Masters are the new Project Managers with a definite ‘No’. Scrum Masters fulfill some of the tasks of a traditional Project Manager, but so do the other members of a Scrum team, i.e. the Product Owner and the development team. Should PMs become SMs then? Possibly. However, it requires a lot of discipline of the PM not to try to manage the team, and not to tell them which tasks to tackle next during the Daily Scrums. Since it is the SM’s responsibility to enforce the Scrum process there is no-one to correct the PM in case he falls back into the old rut. It is more common that SMs are recruited from within (while possibly still being part of) the development team.
Consequently, is there no place for Project Managers in Scrum? I shall cover this question in my next entry.
