🎉 October Learning Month — learn a new software term every day!
An interactive flashcard trainer for software engineering terms.

Retrospective

In plain terms

A meeting to reflect on and improve the team's process.

Going deeper

A retrospective gathers the team to discuss what went well, what didn't, and what to change, driving continuous improvement. It's structured self-reflection.

Under the hood

Held at iteration end; effective retros produce concrete, owned action items, not just venting.

Examples

Sprint retro, process improvement, lessons learned, action items, Agile.

Think of it like...

Like a post-game review where the team plans how to play better next time.

Feedback & Bug Report