Who is managing the Scrum Team? Who makes decisions about development work? Who decides on the releases? Where is the line between a Scrum Master and a Product Owner? Who plays the role of a manager in a Scrum team?
Sounds familiar? So what if I told you that a Scrum team has in fact three managerial roles?
I do agree that at first glance, it may seem messy to have three managers in one project. However, when we look closer at their areas of interest, it becomes clear that even though they work towards a common goal, their areas of interest are quite different. Just take a look:
Thanks to this division, the Scrum “managers” do not step on one another’s toes. The Product Owner shapes the vision of the product. The Scrum Master sketches the frames of work. And the Development Team? They every right to decide on how to do their work within the frames given by the Scrum framework and product requirements.
“A manager’s most important work is helping the people doing the work. Give them a goal and let them work. Remove any impediments that get in their way. Do anything that may make them more effective or productive. Then the organization can capitalize on the fruits of their work.” (Ken Schwaber, Software in 30 Days: How Agile Managers Beat the Odds, Delight Their Customers, And Leave Competitors In the Dust)
In this understanding there is no place for overlapped responsibilities since the responsibility of all members of the Scrum team is to help one another doing their work to achieve the main goal: delivering working and valuable software at the end of each sprint.