What does "retrospective" mean in programming?
retrospective is one of the most common terms in software development. This guide explains what it means, how it is used in practice, and why it matters, with real examples from the developer world.
Definition
A meeting held at the end of each sprint where the team reflects on how they worked together. The team discusses what went well, what did not go well, and what to improve in the next sprint. Retrospectives are about the process, not the product. Often shortened to 'retro'.
Example
"In the retrospective, the team agreed to add more automated tests after three bugs slipped into production."
Can you put this sentence in the right order?
Keep building your technical English
You just looked up what this word means. Lingua-e turns vocabulary like this into full practice: fill-in-the-blanks, listening, and real developer conversations.
Practice this for free