Sprint retrospective in Software Engineering - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of a Sprint retrospective?

The main purpose of a Sprint retrospective is to reflect on the past sprint to identify what went well, what didn’t, and how the team can improve in the next sprint.

beginner

When does a Sprint retrospective usually take place?

A Sprint retrospective usually takes place at the end of a sprint, after the Sprint Review and before the next Sprint Planning.

beginner

Name three common questions asked during a Sprint retrospective.

Common questions include: What went well? What didn’t go well? What can we improve for the next sprint?

beginner

Who participates in a Sprint retrospective?

The entire Scrum team participates, including the Scrum Master, Product Owner, and Development Team members.

intermediate

How does a Sprint retrospective help improve team performance?

By openly discussing successes and challenges, the team can agree on actionable improvements, fostering continuous learning and better collaboration.

What is the main goal of a Sprint retrospective?

A To reflect on the sprint and improve processes

B To review the product backlog

C To assign tasks to team members

D To plan the next sprint

The Sprint retrospective focuses on reflecting on the sprint to find ways to improve team processes and collaboration.

Who usually facilitates the Sprint retrospective?

A Scrum Master

B Product Owner

C Project Manager

D Development Team Lead

The Scrum Master typically facilitates the Sprint retrospective to ensure it runs smoothly and stays focused.

When is the Sprint retrospective held in the Scrum cycle?

A At the start of the sprint

B During the sprint review

C At the end of the sprint

D Before the sprint planning

The Sprint retrospective is held at the end of the sprint, after the Sprint Review and before the next Sprint Planning.

Which of the following is NOT a typical question in a Sprint retrospective?

A What went well?

B What didn’t go well?

C What features should be added next?

D What can we improve?

Deciding on new features is usually part of backlog refinement or sprint planning, not the retrospective.

What is a key benefit of conducting Sprint retrospectives regularly?

A Faster coding speed

B Continuous team improvement

C More detailed documentation

D Increased budget

Regular retrospectives help teams continuously improve their processes and collaboration.

Explain the purpose and timing of a Sprint retrospective in Scrum.

Think about when the team looks back on their work and plans to do better.

Describe who participates in a Sprint retrospective and why their involvement is important.

Consider the roles in Scrum and how they contribute to improvement.