PROJECT MANAGER TO SCRUM MASTER

TRANSITION FROM PROJECT MANAGER TO SCRUM MASTER ROLE

Most Organizations who transition from a Waterfall to an Agile model will have a number of Project Managers who move into Scrum Master roles. While the individual would have acquired a Scrum Master certification and understood the responsibilities that a Scrum Master role demands, the major shift is needed in their mindset.

Here are a few tips for making a smooth transition from a Project Manager role to a Scrum master role.

1.    Realize the difference in Project Manager v/s Scrum Master roles

Project managers are the drivers of their teams. They are like the coxswain of a rowing crew. The rowers face backward, looking at the coxswain who sits at the rear of the boat facing forward. The coxswain steers the boat but also coordinates the power and rhythm of the rowers. Like a project manager, the coxswain is clearly in charge; they literally can see what the rowers can’t.

A Project Manager directs, encourage, create plans, and ultimately are responsible for the project team’s success. It’s right there in the title: they have direct management responsibility for their teams.

A Scrum Master follows an entirely different paradigm—more like a coach. They neither drive nor manage their teams, but instead help them to be the most successful version of themselves. They assist, they are servant leaders, they help in any way possible. In addition, a Scrum Master is responsible for ensuring the team understands the agile principles and the Scrum framework.

 “A Scrum Master leads through influence, not authority.”

The opposite can be said of a project manager. Understanding this difference is key! If you try to take on the Scrum Master role with the mentality of a project manager, you’re setting yourself up for failure before you even begin.

 

2.    Shift Project Plan language from Deadlines to Estimates

In a traditional project management environment, deadlines are set in stone and the more often your team achieves their deadlines, the better you’ve done as a project manager. You are responsible to push your team to deliver on time, on scope, and on budget—the dreaded iron triangle.

In agile teams, we approach the issue of timelines from a more honest perspective. We face up to the fact that we can’t know for sure how long it will take to do a complex piece of work, much less a string of them.

So we try to project into the future and estimate when something might be done based on real data from the team, and not just a gut assumption. If a team consistently can deliver three to five items every few weeks, we can likely project their future output by multiplying that same range over a period of time.

The key here is that it’s an estimate, not a deadline. The Dev team is not promising that they will complete some huge chunk of work from the product backlog over the next six months. They are estimating, based on their current burn rate (or velocity), where they will be on a certain future date. If their pace changes or the scope changes, they can update that projection which will help the Product Owner to provide the most accurate current forecast to their stakeholders.

This is not to say that we can’t ever have a date set in stone. Every business has dates that can’t move (maybe it has to be done by end of year or for the start of that big industry conference). When dates are fixed like that, we have to be flexible on the scope of our projects, while staying true to the overall product vision. Traditional project management doesn’t allow for it.

As part of being agile, scrum teams often trade scope for schedule.

 

3.    Focus on the Team

If I am a project manager, my focus is on schedules, deadlines, scope, and budget. I am in charge of juggling my resources (not people) and my critical path to ensure the project runs smoothly and according to plan.

If I am a Scrum Master, I am focused on the team. I spend my time thinking of ways to help them improve. I’m on the lookout for interpersonal conflicts within the team. I’m watching for both internal and outward-facing miscommunications. I am in perpetual search of ways to help us get better.

You’ll need to shift your focus to shift your role. Project managers focus on output. Scrum Masters focus on outcomes.

A Scrum team wants to deliver the most value each sprint, knowing this isn’t always the same as the most volume. A Scrum Master helps the team make the biggest impact in the lives of their customers, regardless of the volume. In fact, a Scrum Master would prefer to make a bigger impact with less volume so that they have more availability to tackle other areas. A project manager simply wants to push as much volume as possible through the team.

This team focus goes far beyond productivity. Scrum Masters help resolve conflicts, coach individual team members on their role on the team, and help the entire organization to recognize and respect the benefits of a self-organizing team. It’s a big job and requires a far greater skill set than simply managing a project plan.

The key to project managers becoming successful Scrum Masters is being crystal clear on the differences in the approach to the role (Scrum Master vs project manager vs product owner).

If you are a project manager who enjoys organizing timelines and keeping teams on track for deliverables or who is more interested in product owner responsibilities such as helping shape what will be created, being a Scrum Master may not be the best fit for you. If, however, the part of your job you enjoy most is working alongside a team of dedicated professionals to collaboratively make a difference in your customer’s lives, you’ll likely excel at being a Scrum Master.



 

Comments

Post a Comment

Popular

Application of Scrum Values

The essence of Scrum are the 5 values. A Scrum-Agile project will not be successful unless these values are demonstrated in every event, while preparing every artefact and while performing any role. In fact, these values can be demonstrated in any environment to reap benefits. Here are 10 practical instances for each Scrum value that any team can demonstrate: COMMITMENT Team members dedicate themselves to achieving the team's goals and doing their best work. They commit to the sprint goals and support each other in meeting those commitments. Team commits to delivering specific user stories in the sprint backlog, even when facing technical challenges or scope creep requests from stakeholders. Team members commit to rotating on-call duties to ensure continuous support for critical production systems across different time zones. When a legacy system needs modernization, team members commit to learning new frameworks or cloud technologies requ...
Read more

AGILE Mindset

Do your project teams have an AGILE Mindset? Delivering projects using AGILE as a methodology is no longer 'one' of the options. It is the 'only' option especially for Organizations engaged in IT services, Product & Mobile App development. For that matter, even Organizations in other sectors like manufacturing, Infrastructure and even Consulting are considering delivering some of their projects in an AGILE way. Many Organizations who have implemented AGILE as a methodology have fallen back to other traditional methods or are struggling to make it a standard practice. Having seen a number of AGILE projects from the inside and outside, I have a few thoughts on the common mistakes made by Organizations and project teams when delivering projects the AGILE way. If you are considering going the AGILE way or have encountered challenges while implementing the AGILE way, I have a few probing questions for you. The answers to these questions may hold the key for a successfu...
Read more

Science of Influence

One of the traits that Project Managers or any Leader needs to develop is the ability to influence. Every project ecosystem consists of Stakeholders, internal and external. These include your own team members. The ability of a Project Manager to influence these Stakeholders will ensure that the project is in control. Dr. Robert Cialdini has developed 7 principles of influence which can be used by Leaders to influence others. 1.  Reciprocity :  When you do people a favour, they tend to respond in a manner you want them to. However, there are some points to note. - I t’s not about what is given, but HOW AND WHEN IT IS GIVEN . Be the first to give the favour. - Let it be personalized and unexpected. Tell them ‘ I am doing this only for you ’. Suppose, you have done a favour to a person and he/she says ‘Thank you’. What is your response? Many of us say, ‘Its okay’, ‘It was my duty’ etc. Some rare person may say ‘Now you also owe me a favour’.  Instead use this principle Respo...
Read more