Wednesday, June 25, 2008

What's the difference between a Project Leader and a Scrum Master?

This is a serious question ;-)

I just led a workshop for a medium size company which was considering (and is now planning) to start using Scrum as the organizing principle for their SW Development efforts. And exactly this question arose.

As it was, we had a classically trained project manager in the room, so he provided much insight into what is expected of a project manager:
  • Select Team Members
  • Select Tools
  • Plan Tasks
  • Monitor Progress and Sucess
  • Define and Impose Standards
  • Coordinate Work between Team Members
  • Budget
  • Scope
  • Set Priorities
  • Assign Tasks
  • Communicate with the Customer
Explicitly not part of the Project Manager's job is removing impediments.

How is this work distributed among the players in Scrum?

S-MP-OTeam
Select Team Membersinitialonce established
Select Toolssharedshared
Plan TasksX
Ensure satisfactory implementationsX
Define and Impose StandardsX
Coordinate Work between Team MembersX
BudgetX
ScopeX
Set PrioritiesX
Commit to Delivery Datessharedshared
Assign TasksX
Communicate with the Customer (for realization)X
Remove ImpedimentsX


So a Scrum master actually has very little in common with a classically trained project manager. The most important job of the scrum master is to remove impediments, something which is explicitly not part of the project manager's job.

The Scrum master is a 'servant leader' -- his primary job is to ensure that his team can work and that everyone is playing by the rules. He will also be an agent if not the agent of change in his organization: identify what prevents to organization from advancing and eliminating that impediment.

If you are looking for the difference between RUP and Scrum, waterfall and Scrum, or almost anything and Scrum, look first at the roles. Here is where the fundamental differences are to be found.

6 comments:

Michael Dubakov said...

Well, I tend to disagree that "remove impediments" is not a part of Project Manager's job. I was a PM several years ago and this was my primary goal that times. Some good books on PM like explicitly mention that. Also here is one nice quote: "Rather than just removing obstacles when they appear, a better Project Manager prevents them from appearing" :)

Peter said...

I was actually surprised by this assertion too. The response was that the PM ensures that impediments are addressed, not that s/he actually addresses them him/herself.

I'm curious what RUP has to say on this subject...

Alex said...

It's odd to me that people would expect the Scrum Master to be in contact with the client (since most impediments need to be resolved ultimately by the client, in my experience), I would think the Scrum Master would be in charge of whipping the BA or PM into action to remove impediments.

Peter said...
This comment has been removed by the author.
Peter said...

I'm not surprised by it at all.

For example, at a former employer of mine, the project leader was the eyes, ears and mouth of the project; the techies were its arms and legs. So the PL was expected to talk to the customer (gather & spoon feed information to the techies, communicate news especially bad news, to the customer.

So there is conflict potential between the Scrummaster's role as a facilitator and the team's expectation that a "project leader" be the interface to the customer.

Peter said...

Hi Michael,

Just for fun, I went googling for Project Manager Job Descriptions.

This one and that one were among the top links. Both largely confirmed the definition of the Project Manager.

Apparently handling impediments ("issues") is more the job of the program manager than the project manager.