Management Scrum
The notion of management when talking about a Scrum Team is much more vague and less important if we compare it with traditional management of development teams. Some even think that it is the Product Owner who acts as a manager. It is partially true. But a typical (traditional) manager doesn’t have the same responsibilities as a Product Owner does.
As both notions (manager and management) are rather broad, Scrum treats them as a kind of a shell, which envelops the whole working process of a Development Team, but doesn’t influence it directly. A Development Team has no direct contact with the Management. A Scrum Master, a Product Owner or a Stake Holder can perform this function. For example, a Scrum Master can contact the Finance dept., if there are any obstacles, getting in the way of his team. Finance dept., are not managers in the direct sense, but they can maintain the working process of the Development Team.
In order to understand the structure, let’s take a look at the picture.
Scrum Team
Scrum Team – is a collective image of a Team, which consists of a Development Team, a Scrum Master and a Product Owner. The Team is self-sufficient and doesn’t depend on any kind of outsource specialists or clients.
Product Owner
A Product Owner is a link between the Client and the development Team. He has the authority to make final decisions withing a Scrum Team
Development Team
We tend to think that a 'work unit' means a single person, if we talk about human resources. But in Scrum it is a bit different: it is the Development Team which is a work unit.
Scrum Master
Let’s try understand once and for all what does the notion Scrum Master mean and what are the duties of a Scrum Master.
Stake Holders
One of the most important events of Scrum is the Scrum Planning Meeting. A Product Owner, a Scrum Master and the whole Development Team take part in it. Sometimes, but not very often, stakeholders are also present during the meeting.
