Are there PMs in Scrum? No (but…)

This content is syndicated from LeanAgileTraining by Joe Little. To view the original post in full, click here.

Scrum has only 3 roles: Product Owner, ScrumMaster and Implementer.

Who is responsible for ‘the project’?  Well, that would be the whole Team.

What do we do with George, who was a Project Manager (PM)?  Well, we have to talk to George, but maybe he would make a great ScrumMaster or a great Product Owner.  Or something else.

The ones who liked removing impediments tend to make good SMs. The ones who liked managing the requirements often make good POs.

Next, several comments.

1. Some of the best agile people I know were Project Managers once.  (I was one once.)

2. It is very common for the phrase ‘project manager’ to imply to some people that that person is ‘responsible’ for project success.  This is not the case with agile. The whole Team is responsible. Together.  Each person in a slightly different way. But, they win together or they lose together.

Now, often the PM knows well that only the Team has success. And sometimes the Team also understands this well. But as soon as we call someone ‘PM’, then a manager outside the Team starts talking as if this is George’s project to win or lose. And it starts to hurt things, hurt the chances for success. So, I suggest avoiding the term completely.

It is a nice idea that one person only could be responsible. It might seem to make another manager’s work easier.  And maybe in some areas, it is true. But in our knowledge work, the whole Team must contribute. So, they win or lose as a Team.

3. Some PMs have years of experience trying to drive a ‘team’. They have their checklists. They have their command-and-control ways. I think this way of working is wrong, both as a way to treat people, and as a way to success. In any case, it is not what we do in Scrum.  And, many PMs cannot break these habits. So, watch out for that.

4. Scrum is a simple framework. Scrum does not even try to give the Team, by itself, everything that the Team will need to succeed.  They Team is expected to add things to Scrum, appropriate things for their work and their situation.

In this regards, many PMs have dealt with and studied many of these ‘possible things to add’.  So, often George is good at suggesting these things. And other things can also be suggested by other ‘disciplines too.

5. Some companies still have PMOs after getting well started in Scrum. (PMO means Project Management Office, although I find each PMO group…usually several PM types grouped together…each PMO group can be run quite differently.)  This may not be the best pattern, but it is not clear that this is a terrible pattern. Or at least, it might be a necessary pattern for a temporary period.  In any case, some PMs can still work in a PMO kind of office, and this does not seem to be totally contrary to Scrum, or to clearly hurt Scrum teams. (But there are occasionally issues.)

6. Most of the duties of the old PM are divided in Scrum amongst the PO, the SM, and the Team.

7. Should we put George (a PM) on a Team that already has a PO and a SM?  And give George mainly his old PM duties?  (We could make a long list of those….)  No, it seems very unlikely this will work well. George will be in too much unnecessary conflict with the PO and the SM. And, while there may be a few other duties, they are not enough to keep George busy full-time.  Maybe, in a system that still also demands Teams to comply with waterfall reporting, maybe then there is enough work for George (the former PM) as a ‘pig’. Maybe. But we ought to get away from that as soon as possible.

8. Could Scrum Teams in large organizations need help doing ‘project management reporting’ and such?  Yes. And often George has a great role to assist several teams in handling this work.  In this case, we might say George is a ‘chicken’ to several teams.  Still, we would hope that most of this role would go away with time.

Leave a Reply

Your email address will not be published. Required fields are marked *

5 + fourteen =

There are 101 ways to do anything.
To find the best way, sometimes you need expert help

What People Say

“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”



To explore how we can help you, please get in touch