Business analysis glossary
Retrospective Action
What it is
A retrospective action is a specific improvement a team commits to after a retrospective or lessons learned session. A good action names what will change, who owns it and by when, so it can be checked at the next session rather than forgotten.
Why it matters
Retrospectives without actions become complaint sessions, and teams stop taking them seriously. One or two concrete actions per session, followed up, lead to steady improvement. Analysts often own actions related to requirements, such as adding a definition of ready check or inviting testers to refinement.
Example
In the sprint retrospective, the team agrees that unclear stories caused rework. The action is specific: from next sprint, Pooja will run a fifteen minute three amigos check on every story before planning, and the team will count how many stories bounce back. Two sprints later, rework has halved.