The team normally consists of 4–6 persons (including Product Owner) – a group size that experience and research has shown to be best for this type of work.
The team members decide how the work should be done and how assignments are distributed between each other. The are responsible of delivering the features they commit to according to engineering best practices and the project’s/team’s Definition of Done. The team is cross functional which means they can deliver a feature from start to end including backend development, frontend development and quality assurance. Though there are different types of experts in a team – each team member is encouraged to swap tasks with another member to broaden each team members skills.
The product owners responsibilities and job tasks are:
Represents the voice of the customer and ensures that the scrum team works with the right things from a business perspective. Clearly expressing Product Backlog items. Ensuring the Development Team understands items in the Product Backlog to the level needed.
Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next. Have a vision of what he or she wishes to build, and convey that vision to the scrum team.
Maintain a prioritised backlog of features and bugs. Prioritised in order of business value.
Attend the sprint planning meeting and present the backlog in order of priority and answer questions from the team. Be available to the team during the sprint to answer questions.
Attend the sprint demo and accept or reject each demoed feature or bug fix.
It’s good if the product owner also attends the daily scrum meeting to be available for questions from the team.
The scrum master’s responsibilities and job tasks are:
Be a process owner of the team and make sure the standard work process set by the company and the team itself is followed. Helping the Scrum Team understand the need for clear and concise Product Backlog items.
Facilitate the meetings: Backlog refinement, Sprint planning, Daily Scrum, Sprint Demo, Retrospective.
Listen to the teams impediments in each daily scrum and work to remove the impediments.
Constantly coach the team in the scrum process.
Protect the team and the sprint from outside interference.
Follow up and remind and make sure the team follows through on the actions from previous retrospective.
Responsible for finding robust technical solutions designs for the team and prevent reinventing the wheel and preventing too optimistic or too pessimistic estimates.