Run a sprint retrospective with three simple columns: what went well, what could improve, and the action items that come out of it.
A retrospective is only useful if it changes something. Keeping What Went Well separate from What Could Improve makes sure the team also recognizes what to keep doing, not just what went wrong, while a dedicated Action Items column keeps the conversation from ending in vague agreement without any actual next step. Promoting a note directly from Could Improve into Action Items is a small nudge to close that gap during the meeting itself.
A note like "communication was hard" is harder to act on than "the design handoff was missing context."
Two or three concrete actions a team will actually follow through on beat a long list that gets ignored.
A regular team meeting, common in agile workflows, where a team reflects on the last sprint or period of work and identifies what to keep doing and what to change.
It copies that note into the Action Items column, so a proposed improvement can be turned into something the team commits to.
This board keeps one active retro at a time. Click New Retro to clear it, or copy the contents elsewhere first if you want to keep a record.
In your browser's local storage on this device, until you clear your browser data or click New Retro.
More handy tools from My Panda Toolbox.