Roles

Scrum Team Structure

Which roles are part of a Scrum team?

• Product Owner

  Scrum Master

  Development Team

• Project Manager

  Business Analyst

  Developer

• Product Owner

  Project Manager

  Developer

• Scrum Master

  Project Manager

  Developer

Roles

Role Responsibilities

What are the key responsibilities of the Product Owner?

• Writing code and testing

• Defining and prioritizing the product backlog, ensuring the team delivers value to the business

• Managing the team's daily tasks

• Conducting performance reviews and providing performance feedback back to the Development Team

Roles

Development Team

In the Scrum framework, what is the primary responsibility of the Development Team?

• Creating a potentially releasable product increment.

• Ensuring that the team follows Scrum rules.

• Prioritizing and allocating the Product Backlog

• Stakeholder communication and managing their expectations.

Roles

Scrum Master Duties

How does the Scrum Master Support the Development Team?

• Assigning tasks to team members

• Removing impediments, ensuring the team follows Scrum practices, facilitating meetings

• Providing technical training and guidance

• Approves leave requests and handles staff shifts

Events

Sprint Planning

What are the main goals of Sprint Planning?

• To plan which user stories and test cases still need to be written.

• To plan the logical fulfillment of the user stories within the upcoming sprint.

• To review the work from the previous sprint and reflect on what went well in the team.

• To ask questions about the user stories and define them.

Events

Daily Scrum

What is the purpose of a Daily Scrum?

• To provide an opportunity for the Product Owner to look through the output so far.

• To communicate with the team, address any barriers and keep everybody up to date with the progress made.

• To assign new tasks from the backlog to team member.

• To review the project budget, risks and issues log and the project timeline.

Events

Sprint Review

What happens during the Sprint Review?

• The team demonstrates the progress to the stakeholders and discusses next steps

• The team conducts performance evaluations of their work this sprint

• The next sprint is planned and user stories are broken down into tasks

• The team updates the project plan to reflect the work completed

Events

Sprint Retrospective

Why is the Sprint Retrospective important?

• To assign tasks for the next sprint to the Development Team.

• To review the project timeline and ensure the team is on track to meet the project deadline.

• To update the product backlog to reflect the progress made that sprint.

• To allow the team to come together to recognise their achievements and form an action plan to help improve the next sprint.

Artifacts

Product Backlog

What characteristics should the product backlog have?

• It should be ordered, emergent and appropriately detailed

• It should be fixed, detailed and unchangeable

• It should be unordered, detailed and emergent

• It should be ordered, fixed and unchangeable

Artifacts

Sprint Backlog

What does the sprint backlog consist of?

• All tasks for the entire project

• Selected product backlog items for the sprint and a delivery plan

• A detailed project plan and timeline

• A list of each team member's daily tasks for each day during the sprint