The false expectation “I’m a Scrum Master, I can lead a project”

During the last months, I have noticed a lot, people sharing their titles of Scrum and/companies looking for scrum masters to lead agile projects, well, let me tell you this, to be a project manager and to be a Scrum Master/ Product owner, IS NOT THE SAME. But then why people believe they can lead projects with scrum, though scrum does not have a leader? I think this is the misunderstanding of the framework, and the marketing done by the scrum offering companies. But let’s answer “Why?”

1-   The framework of Scrum, says "there is not project manager", then we cannot lead a project, since there is always the need of a leader, being a project manager goes beyond sending update e-mails, for instance:

a.   The PM clarifies the scope, after the initial idea has been documented (lots of time in the Project Charter).

b.   PM negotiates deliverable, timelines and cost.

c.    The PM translates the quality expectations based on what the customer expects (saying “the pizza needs to be warmed”, is not the same as “the pizza needs to be cooked at 250ºC”).

d.   Etc

2-   The guide of scrum just tells you how to think, in a nutshell, it is “Split the deliverables in workable assets”, how, why, when is not the SM who does it, it is the team, so the SM loses complete control of the project.

3-   Scrum does not explain, where the materials come from, or the computers to program, or when and how hire people, what if some legal requirements are needed, how to present to the clients, when to do the meetings, and most import "How much does it cost? vs how much can I spend?", all done by PM, but as per scrum, all appears magically, and the Product Owner just arrives sets the expectations and all starts.

4-   Scrum does not tell you, when the contract is sign, what to do with the agreements, how to identify the correct stakeholders, how to provide with reports for the sponsors, how to manage the sponsor, how to close the project, etc.

a.   This is not explained in the product owner role either.

I might continue but, I think the point is cleared, if you want to lead a project, being a Scrum Master, is not the path.

So what is a “Scrum Master” and what’s its value?

A scrum master is a lead on knowledge, that helps people on understanding the concept, and helps the team on getting straight their goals, without interfering but helping them see how to the best decision. Helps removing impediments or constrains that inhibit the delivery completion.

Does a “Scrum Master” has a vote on the scope of the project?

As per the guide, not really, they just provide with the critical thinking, if you want to be part of a group that creates great ideas for projects, a SM is not your path.

Can a PM and SM work together?

Of course and that is the best idea when using Scrum, combine it with a Project Management Methodology, in my case I like it more with PRINCE2.

Price2 explains that the PM creates all scope and deliverable information, but a “Team Manager” distributes the information among the “Delivery team” to create the product, this delivery manger or team manager I see it as the Scrum Master, who distributes with help of his team all the efforts required.

In a nutshell, Scrum is useful, if you know how to combine it with a project manager methodology, such as PMP or PRINCE2, otherwise, it just becomes a nice to have in a curriculum, making it look bigger, but worthless, in real life if you followed as per the book.

About the author

Andrey Mendez + 7 years of experience in Quality and Project management. Certified as: Quality Engineer, 6 sigma Black Belt, PMP, PRINCE2, ITIL & ScrumMaster/Product Owner, ISO 9001/27001 internal auditor.