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.

Practice

1. What is the main purpose of a sprint retrospective in Agile?

easy

A. To plan the tasks for the next sprint

B. To review the project budget

C. To assign roles to team members

D. To reflect on the sprint and find ways to improve

Solution

1. Step 1: Understand the sprint retrospective goal

   The sprint retrospective is a meeting held after a sprint to reflect on what went well and what can be improved.

2. Step 2: Differentiate from other sprint events

   Planning tasks and assigning roles happen in other meetings like sprint planning, not retrospectives.

3. Final Answer:

   To reflect on the sprint and find ways to improve -> Option D

4. Quick Check:

   Retrospective = Reflect & Improve [OK]

Hint: Retrospective means looking back to improve [OK]

Common Mistakes:

• Confusing retrospective with sprint planning
• Thinking it's for assigning tasks
• Believing it's about budget review

2. Which of the following is a correct step in conducting a sprint retrospective?

easy

A. Gather data about the sprint

B. Write the final project report

C. Assign new team members

D. Create the product backlog

Solution

1. Step 1: Identify typical sprint retrospective steps

   Common steps include gathering data, discussing insights, and planning improvements.

2. Step 2: Eliminate unrelated activities

   Writing final reports, assigning members, or creating backlog are not part of retrospectives.

3. Final Answer:

   Gather data about the sprint -> Option A

4. Quick Check:

   Retrospective step = Gather data [OK]

Hint: Retrospective starts with collecting sprint info [OK]

Common Mistakes:

• Mixing retrospective with project closure tasks
• Confusing backlog creation with retrospective
• Thinking team assignment happens here

3. Consider this scenario: During a sprint retrospective, the team identifies that communication was poor. What is the most likely next step?

medium

A. Discuss and plan actions to improve communication

B. Ignore the issue and continue as usual

C. Change the sprint goal immediately

D. Assign blame to specific team members

Solution

1. Step 1: Understand retrospective purpose

   The team reflects on issues to find improvements, not to ignore or blame.

2. Step 2: Identify appropriate action

   Planning actions to improve communication fits the retrospective goal.

3. Final Answer:

   Discuss and plan actions to improve communication -> Option A

4. Quick Check:

   Retrospective = Plan improvements [OK]

Hint: Retrospective leads to improvement plans [OK]

Common Mistakes:

• Ignoring problems found
• Blaming individuals instead of process
• Changing sprint goals mid-retrospective

4. A team forgot to hold a sprint retrospective at the end of their sprint. What is the best way to fix this mistake?

medium

A. Skip the retrospective entirely and move on

B. Hold the retrospective as soon as possible after the sprint

C. Cancel the next sprint to make up for it

D. Replace the retrospective with a status report

Solution

1. Step 1: Recognize importance of retrospective timing

   Retrospectives should happen after each sprint to reflect and improve.

2. Step 2: Find best corrective action

   Holding it as soon as possible keeps the feedback relevant and useful.

3. Final Answer:

   Hold the retrospective as soon as possible after the sprint -> Option B

4. Quick Check:

   Missed retrospective? Do it ASAP [OK]

Hint: Do missed retrospectives quickly after sprint ends [OK]

Common Mistakes:

• Skipping retrospectives
• Thinking cancellation of sprint fixes it
• Confusing retrospective with status reports

5. A team uses a sprint retrospective to identify that their testing process is too slow. How can they apply this insight effectively?

hard

A. Reduce the number of tests to save time

B. Ignore the issue since testing is always slow

C. Plan to automate some tests in the next sprint

D. Assign testing only to one team member

Solution

1. Step 1: Understand retrospective action planning

   The team should create actionable plans to improve identified problems.

2. Step 2: Evaluate options for improving testing speed

   Automating tests is a practical way to speed up testing without sacrificing quality.

3. Step 3: Avoid harmful shortcuts

   Ignoring, reducing tests, or overloading one person can cause bigger problems.

4. Final Answer:

   Plan to automate some tests in the next sprint -> Option C

5. Quick Check:

   Retrospective insight = Plan automation [OK]

Hint: Turn problems into action plans, like automation [OK]

Common Mistakes:

• Ignoring issues found
• Cutting testing scope unsafely
• Overloading single team member