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.