Scrum Master vs Project Manager

It's an interesting question. The moment you equate a Scrum Master to a Project Manager that means one of those roles is misunderstood. To understand these roles, it's essential we first understand the difference between a Product and a Project. Products are solutions to people's problems like a pouch that holds markers, a bag that helps to carry vegetables, and a chatting software that allows people to communicate. The products exist as long as people use products. The organizations that build Products continue to uncover user needs as they use the products and enhance and release new product versions often.  

However, if we look at the definition of a Project, per PMI PMBOK, it is temporary in that it has a defined beginning and end in time, and therefore set scope and resources. For example, when you hand over the design of a town hall or a theatre to a Civil contractor to build, the scope is set, the cost is set (well you wish), and the time is set (wishful thinking never stops). Well, although the scope is set, the cost and time can vary based on many factors like industry trends affecting the cost of goods, and weather conditions affecting the timeline. However, the scope is very well known. So, the thought process here is to reduce time and cost. If we talk in terms of product contexts or domains, this falls in a complicated context (Requirements are known, but the solution is not well known). Hence applying the right skills to the right tasks can help in reducing time and cost. Projects like migrating from mainframe to open stack, and customizing a newly designed autonomous car per customer needs dwell in this territory. These are Projects, and project thinking is very useful there. 

Products, on the other hand, dwell in complex contexts (unknown problems hence unknown solutions) like designing a new autonomous car, finding a cure for COVID-19, and building new software. Given the requirements are unknown, the processes should enable quick learning and pivoting. The system (processes, team structures, policies, tools, etc.) should allow quick and continuous learning in this context.  

Now, with this context, let's look at the roles generally: You can categorize roles into 3 categories 

1. Business-focused: Roles that focus on building business and increasing ROI for organizations like CEOs, Product Managers, Business Development, Marketing, etc. 

2. Product-focused: Roles that are focused on building the solution and productizing them like CTOs, Architects, Programmers, Test Engineers, etc. 

Where would you fit the Project Manager in these roles? What do Project Managers focus on?  

Project Managers are the owners of the Project, responsible for seeing it through to completion. They are the ones who inspire the project teams with a sense of shared purpose and connect them with all the stakeholders to achieve the ultimate goal of the Project. They focus on maximizing the ROI of the Project by balancing triple constraints (cost, time, and scope). Although they get involved in building the projects, their focus is on maximizing the value (ROI) of the Project.  

What kind of role is Scrum Master?   

Scrum is an empirical process framework that is used for solving complex problems. Scrum is an emergent practice that evokes Product Thinking in product teams to continuously learn about the problem to be solved and uncover the solution. A complex domain is a different territory than what Project Manager dwells in, a complicated context where at least the scope is well known. In this context, just having skill is not enough, but team cognition and willingness to run quick experiments are crucial. One needs to build a learning system to enable teams to embrace such emergent practices. Scrum Masters are the ones who are responsible for building such a system. Scrum Master's role is System-focused, unlike the Project Manager's role, which is Business-focused. Learn more about Scrum Master's role here, 

If you were to find a role that's focused on Systems in Project set up, who would that be? Project Management Office, right? Per PMBOK, the Project Management Office (PMO) is defined as "a management structure that standardizes the project-related governance processes and facilitates the sharing of resources, methodologies, tools, and techniques". Well, I'm not saying PMO is like a Scrum Master. They operate in different contexts. All I'm saying is they are on the same side of the focus area in their own contexts.  

Now, who is focused on Business in a Scrum environment? It's the Product Owner. Of course, Project Managers can't go on to become Product Owner, as the skills and responsibilities to maximize ROI in a complex domain are much more different than in a projected complicated domain. However, Project Managers (true ones) are best suited to become a PO by acquiring additional skills required for a Product Owner. Learn more. 

With 11+ years of experience in the field, Leanpitch has successfully upskilled 90,000+ people across 12+ countries. Explore our website, Our trainers are internationally acclaimed for their insightful and experiential training.

We upskill and boost your career by providing a wide range of courses such as CSPO, CSM, ICP-ACC, etc. visit our website to learn more about all the courses we offer.