Skip to content
Ever Works

Retrospective Practice

A regular team or personal reflection practice borrowed from Agile to review what went well, what didn't, and what to improve, enabling continuous learning and process optimization.

Last updated: 2026-03-10 12:21

What is a Retrospective?

A retrospective is a regular meeting or practice where a team (or individual) reflects on recent work to identify improvements and celebrate successes.

Origin

Part of Agile/Scrum methodology, typically held at end of each sprint.

Core Questions

  1. What went well? (Continue)
  2. What didn't go well? (Stop)
  3. What should we try? (Start)

Frequency

Team Retrospectives:

Personal Retrospectives:

Format

Team Retrospective Structure:

1. Set the Stage (5 min)

2. Gather Data (10 min)

3. Generate Insights (15 min)

4. Decide Actions (15 min)

5. Close (5 min)

Personal Retrospective Questions

Weekly:

Monthly:

Quarterly:

Benefits

Best Practices

Create Psychological Safety

Focus on Actionable Improvements

Mix Up Formats

Track and Measure

Common Formats

Start, Stop, Continue

What should we start/stop/continue doing?

Mad, Sad, Glad

What made us mad/sad/glad this sprint?

4 Ls

What did we Liked, Learned, Lacked, Longed for?

Sailboat

What's the wind (helping)? What's the anchor (holding back)?

Time Tracking Integration

Review in Retrospective:

Use Data:

Making It Stick

Schedule It

Make it a recurring, non-negotiable event.

Take Notes

Document insights and actions.

Follow Through

Actually implement improvements.

Review Previous Actions

Start each retrospective reviewing last one's actions.

Who Benefits

Related Concepts

Related Items