Roles
There are three core roles and a range of ancillary roles—core roles are often referred to as pigs and ancillary roles as chickens (after the story The Chicken and the Pig).
The core roles are those committed to the project in the Scrum process—they are the ones producing the product (objective of the project). They represent the scrum team.
- Product Owner
- The Product Owner represents the stakeholders and is the voice of the customer. He or she is accountable for ensuring that the team delivers value to the business. The Product Owner writes (or has the team write) customer-centric items (typically user stories), prioritizes them, and adds them to the product backlog. Scrum teams should have one Product Owner, and while they may also be a member of the development team, it is recommended that this role not be combined with that of the ScrumMaster.
- Development Team
- The Development Team is responsible for delivering potentially shippable product increments at the end of each Sprint. A Development Team is made up of 3–9 people with cross-functional skills who do the actual work (analyse, design, develop, test, technical communication, document, etc.). The Development Team in Scrum is self-organizing, even though they may interface with project management organizations (PMOs).
- ScrumMaster
- Scrum is facilitated by a ScrumMaster, who is accountable for removing impediments to the ability of the team to deliver the sprint goal/deliverables. The ScrumMaster is not the team leader, but acts as a buffer between the team and any distracting influences. The ScrumMaster ensures that the Scrum process is used as intended. The ScrumMaster is the enforcer of rules. A key part of the ScrumMaster's role is to protect the Development Team and keep it focused on the tasks at hand. The role has also been referred to as a servant-leader to reinforce these dual perspectives. The ScrumMaster differs from a Project Manager in that the latter may have people management responsibilities unrelated to the role of ScrumMaster. The ScrumMaster role excludes any such additional people responsibilities.
The ancillary roles in Scrum teams are those with no formal role and infrequent involvement in the Scrum process—but nonetheless, they must be taken into account.
- Stakeholders
- The stakeholders are the customers, vendors. They are people who enable the project and for whom the project produces the agreed-upon benefit that justify its production. They are only directly involved in the process during the sprint reviews.
- Managers
- People who control the work environment.
Read more about this topic: Scrum (development)
Famous quotes containing the word roles:
“There is a striking dichotomy between the behavior of many women in their lives at work and in their lives as mothers. Many of the same women who are battling stereotypes on the job, who are up against unspoken assumptions about the roles of men and women, seem to accept—and in their acceptance seem to reinforce—these roles at home with both their sons and their daughters.”
—Ellen Lewis (20th century)
“A concern with parenting...must direct attention beyond behavior. This is because parenting is not simply a set of behaviors, but participation in an interpersonal, diffuse, affective relationship. Parenting is an eminently psychological role in a way that many other roles and activities are not.”
—Nancy Chodorow (20th century)