Roles and responsibilities
Scrum Team
The Scrum team consists of a self-steering development team, a Product Owner and a Scrum Master.
Development team
The development team is a multidisciplinary team. That means it consists of a combination of roles and areas of expertise:
- Interaction designer
- Visual designer
- Architect
- Front-end developer
- Back-end developer
The team is jointly responsible for the following:
- Delivery of 'product' at the end of the sprint.
- The product meets the requirements of the Product Owner.
- Estimating the complexity of work/user stories during sprint planning.
- Informing the Scrum Master/Product Owner of impediments.
Product Owner
- Is member of the Scrum team.
- Represents stakeholders and the business within the scrum team.
- Determines and monitors the scope of the project.
- Writes the user stories and is capable of explaining the content to the development team.
- Is available to the development team for review and other questions.
- Prioritises the backlog so the team can prepare the sprint.
- Takes the lead in the demos.
Scrum Master
- Is member of the scrum team.
- Guides and monitors the scrum process.
- Initiates and facilitates the scrum meetings (Daily, Planning, Review and Retrospective).
- Motivates the team towards self-management.
- Removes impediments or escalates these to the Product Owner.
- Supports the Product Owner.
Your role vs. my role
- Define your own and the other roles by answering the following questions:
- What are 2-3 important deliverables, tasks or other ways you help the team?
- What kind of support do you need and from which role?
- Share and compare notes in order to come to an agreement.
- Use dot votes in order to define the most important deliverables and tasks.
- Draw different circles on the board each representing a role.
- Use the dot voted sticky notes to annotate each role with their most important deliverables, tasks and responsibilities.
- Draw interaction lines between the different roles; use thick lines to indicate most important interactions.
- As a facilitator, make sure that you capture and summarise and ask questions when something is vague.
- At the end of the session everybody should have come to an agreement.
- Write all the conclusions in an email and send it around to make sure that everybody has the same information and that you have something you can fall back on