What is a Sprint Retrospective?

The video explains the concept of a Sprint Retrospective within the Scrum framework, highlighting its purpose to improve team effectiveness. It details who should attend, including the Scrum Master, Product Owner, and Development Team, and notes that stakeholders usually attend only if invited. The video distinguishes between Sprint Retrospectives and Sprint Reviews, emphasizing the focus on team processes rather than outcomes. It outlines the role of the facilitator, typically the Scrum Master, and the typical duration of the meeting. The video also covers the adaptive nature of project management, where teams learn from past experiences to improve future workflows.

What is the primary purpose of a Sprint Retrospective in the Scrum framework?

• To improve team effectiveness and collaboration

• To assign tasks to team members

• To plan the next Sprint

• To demonstrate the product to stakeholders

Who typically facilitates a Sprint Retrospective?

• The Scrum Master

• A Stakeholder

• The Product Owner

• A Development Team member

During a Sprint Retrospective, what is the team primarily focused on?

• The outcomes achieved

• The processes and practices used

• The product features

• The stakeholder feedback

Which of the following questions is typically addressed in a Sprint Retrospective?

• What went well during the Sprint?

• Who should be promoted?

• How can we increase sales?

• What new features should be added?

How can suggestions from a Sprint Retrospective be utilized?

• They are discarded after the meeting

• They are added to the product backlog

• They are integrated into the Sprint backlog for future sprints

• They are used to evaluate team members