SELF-GUIDED BA PRACTICE Packages available · Access after confirmed paymentSee packages ↗

Business analysis glossary

Sprint Retrospective

What it is

The sprint retrospective is the Scrum event at the end of each sprint where the team reflects on how it worked: people, interactions, processes, tools and the definition of done. The team identifies what went well, what could be better and agrees a small number of improvements to try in the next sprint.

Why it matters

Continuous improvement is how good teams become great. A retrospective is the team's regular chance to fix its own problems, such as unclear stories or slow reviews. Analysts benefit from honest feedback on their requirements and from agreeing working agreements with developers and testers.

Example

In a retrospective at Skylark Software, testers say acceptance criteria often miss error cases. The team agrees to hold a short three amigos session for every story before development starts. Two sprints later, defects found in testing have fallen noticeably, and the practice becomes part of the definition of ready.

Used in these guides

CHECK BEFORE CONTINUING

Keep your work safe