Skip to main content

Responsibilities in Scrum, or Why Scrum Developers Should Get Paid More!

Scrum Responsibility Matrix
During last week's CSM/Jumpstart in Bern, Andreas Schliep and I were asked for a "RACI" -- a responsibility matrix for Scrum. We turned the question around and asked our participants to come up with one. Using dot-voting, they identified who is responsible for the following:
  • Selecting Team Members and Tools
  • Planning Tasks; Ensuring good implementations
  • Defining and Imposing Standards
  • Budget, Scope, Priorities, Coordinating Work
  • Commit to Delivery Dates (release)
  • Assign Tasks; Customer Communication
  • Remove Impediments; Reporting
  • Change Management; Risk Management; Compliance
  • Return on Investment; Improving Performance 
A couple of interesting things were visible from the poll (excel Scrum Responsibility Matrix). First, is a project manager still needed in a Scrum project? No! In a classical approach, the project manager is responsible for (almost) everything, but in Scrum, all of the responsibilities of a project leader are covered. The management facing roles are generally covered by the Product Owner, the getting-things-done roles by the Development Team. What would a separate Project Leader do?

Project Leader vs.
Scrum Leadership Roles
Second, a closer comparison between the Project Manager role and the Scrum leadership roles highlight some important gaps in the classical approach. Who is responsible for ROI? Who is responsible for systematically improving performance? Unfortunately, I didn't ask the latter question, but no one thought the Project Manager was responsible for ROI! Some thought the Product Manager was responsible for ROI, but there were many abstentions.  In Scrum, these duties are clearly delegated.

Several people in the course asked, "Where are we going to find Product Owners in our organizations who can fill the bill?" When I look at the duties of each, it seems the all-singing, all-dancing super-man is the project manager role. The P-O is only responsible for 8 instead of 12 disciplines and gets much more help on the rest. Perhaps people are wary of taking on (or delegating) responsibility for ROI? So, yes, it will be a challenge to find good P-O's, just like it is difficult to find good PL's.

Increased Responsibilities
for Scrum Developers
Third, the role of the developer (and tester, because testing is part of the development process) has been upgraded substantially. In a classical approach, the developer is not really responsible for anything (except when the project is late or buggy, then it is their fault!).

Under Scrum, the development team assumes several responsibilities which used to belong to the project leader: full responsibility for selecting tools, planing tasks, ensuring good implementations, defining and imposing standards, coordinating work, delivering committed scope every sprint, and estimates, and shared responsibility for selecting new team members, communications with the customer, change and risk management, compliance and improving performance.

One of the premises of employee compensation is "equal pay for equal work." Equal work is defined among other things by the educational and experience prerequisites, the job responsibilities, and the extent to which is the work must be supervised, is self supervising and/or supervises others. Clearly Scrum-Team members are substantially more self-supervising, have higher responsibilities and probably need more training and experience to apply modern engineering practices like Test Driven Development or Continuous Integration successfully.

So what do you think? Should a Scrum developer get paid more than a developer in a classically managed project? Do you see signs that this is happening?


manuel aldana said…
You should get paid for the outcome and success of results (of course success has to be somewhat defined...). In my experience (real)-agile teams performed often better. Therefore they should also get rewarded better (it doesn't need always to be the money though). I wouldn't limit this to scrum.
Hello Peter,

Thank you for posting such a great article. RACI/Roles & Responsibilities in scrum is very important and critical where scrum master and project manager both exist. They have many task those have overlap in terms of responsibilities and accountability. I am preparing a detailed list of RACI Matrix for the roles like Development Manager, Scrum Master, Product Owner, QA Manager, Program Manager and Team.

This article really helped me. Thanks once again.
Peter said…
Hi Amit,

Why do you feel a need for a Project Leader if you have a Scrum Team? Given that you have this role, how do you divide their duties?


Popular posts from this blog

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

What is the role of a Business Analyst in Scrum?

When I teach a CSM class, my goal is that my participants go home delighted (and of course that they learn about Scrum, that they are motivated to do Scrum, and can pass the online CSM exam). So after every class, I ask for feedback, in particular what could I do to get a better score. And for the next class, I strive to implement or address two or three of the points raised by my participants.

One issue that was raised was unanswered questions. It is annoying to ask questions and not get answers! Time is limited, so it is not always possible to answer all questions, so I thought, why not answer them on my blog? So here goes, first question:
What is the role of a Business Analyst in Scrum? This question is a challenge because Scrum doesn't answer this question! Scrum is a simple, team-based framework for solving complex problems. The roles and ceremonies in Scrum are designed to ensure that inspect and adapt can occur regularly with complete and correct information. Scrum does not…