Sprint retrospective in Software Engineering - Step-by-Step Execution

Concept Flow - Sprint retrospective

Sprint Ends

↓

Team Gathers

↓

Discuss What Went Well

↓

Discuss What Could Improve

↓

Identify Action Items

↓

Plan Improvements for Next Sprint

↓

Sprint Retrospective Ends

The sprint retrospective happens after a sprint ends, where the team discusses successes, challenges, and plans improvements for the next sprint.

Execution Sample

Software Engineering

Sprint ends
Team meets
Discuss positives
Discuss negatives
Create action items
Plan next sprint improvements

This sequence shows the main steps of a sprint retrospective meeting.

Analysis Table

Step	Action	Discussion Focus	Outcome
1	Sprint ends	N/A	Sprint work completed
2	Team gathers	N/A	Everyone ready to reflect
3	Discuss what went well	Positive aspects	List of successes
4	Discuss what could improve	Challenges and issues	List of problems
5	Identify action items	Solutions and changes	Concrete improvement tasks
6	Plan improvements for next sprint	Applying changes	Agreed plan for next sprint
7	Retrospective ends	N/A	Meeting closed

💡 All steps completed, team has a plan to improve next sprint

State Tracker

Variable	Start	After Step 3	After Step 4	After Step 5	Final
Positives List	Empty	Collected successes	Collected successes	Collected successes	Collected successes
Improvements List	Empty	Empty	Collected problems	Collected problems	Collected problems
Action Items	Empty	Empty	Empty	Defined tasks	Defined tasks
Next Sprint Plan	Empty	Empty	Empty	Empty	Agreed plan

Key Insights - 2 Insights

Why do we discuss both positives and negatives during the retrospective?

Discussing positives helps the team recognize what works well (see Step 3 in execution_table), while discussing negatives identifies areas to improve (Step 4). Both are needed to balance feedback and plan effective changes.

What happens if the team skips identifying action items?

Without action items (Step 5), the team has no concrete tasks to improve, so the retrospective loses its purpose. The execution_table shows action items are key to turning discussion into plans.

Visual Quiz - 3 Questions

According to the execution_table, what is the outcome after Step 4?

A List of successes

B List of problems

C Concrete improvement tasks

D Sprint work completed

💡 Hint

Look at the 'Outcome' column for Step 4 in the execution_table.

In the variable_tracker, when are action items first defined?

A After Step 3

B After Step 4

C After Step 5

D Final

💡 Hint

Check the 'Action Items' row and see when it changes from 'Empty' to 'Defined tasks'.

If the team did not plan improvements for the next sprint, which step would be missing in the execution_table?

A Step 6

B Step 3

C Step 5

D Step 7

💡 Hint

Step 6 is about planning improvements for the next sprint in the execution_table.

Concept Snapshot

Sprint Retrospective:
- Happens after sprint ends
- Team discusses what went well and what can improve
- Identifies action items to fix issues
- Plans improvements for next sprint
- Helps team continuously improve

Full Transcript

A sprint retrospective is a meeting held after a sprint ends. The team gathers to discuss what went well and what could be improved. They identify specific action items to address problems and plan how to apply these improvements in the next sprint. This process helps the team learn and improve continuously. The execution_table shows each step from sprint end to retrospective close, while the variable_tracker shows how lists of positives, problems, and action items develop. Key moments include understanding why both positives and negatives are discussed and the importance of defining action items. The visual quiz tests understanding of outcomes at each step and when action items are created.

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