Agile Scrum Master Certification Exam Prep (CSM) - Sprint Retrospective

The video tutorial explains the sprint retrospective process in scrum, highlighting its importance in evaluating and improving the sprint. It covers the roles of the Scrum Master, product owner, and development team, emphasizing the need for coordination and adherence to scrum fundamentals. The retrospective is a crucial meeting for assessing what went well and planning improvements for future sprints. The Scrum Master plays a key role in ensuring the meeting is productive and time-efficient, guiding the team to follow scrum principles and timelines.

What is the primary purpose of a Sprint Retrospective?

• To plan the next Sprint

• To review the product backlog

• To inspect the team and create a plan for improvement

• To finalize the project

When does the Sprint Retrospective occur in the Scrum process?

• At the end of the project

• During the Sprint Planning

• Before the Sprint Review

• After the Sprint Review and before the next Sprint Planning

What is the duration of a daily standup meeting in a Sprint?

• 30 minutes

• 1 hour

• 15 minutes

• 45 minutes

Who is responsible for ensuring the Sprint Retrospective takes place?

• Development Team

• Stakeholders

• Scrum Master

• Product Owner

What is the role of the Product Owner during the Sprint Retrospective?

• To manage the development team

• To ensure the team follows Scrum fundamentals

• To create user stories and manage business value

• To lead the retrospective meeting

How long is a Sprint Retrospective meeting for a one-month Sprint?

• 4 hours

• 3 hours

• 2 hours

• 1 hour

What is a key responsibility of the Scrum Master during the Sprint Retrospective?

• To assign tasks to team members

• To ensure the meeting is positive and productive

• To update the product backlog

• To finalize the project budget