How do I run a sprint retrospective in LocalPM?
Open Retro, click New Retro, choose an active or completed sprint, and fill in what went well, what could be improved, and action items. Then click Create Retrospective.
LocalPM's Retro page records the outcome of a sprint retrospective in three columns: what went well, what to improve, and action items. Each retro is linked to a sprint, so you can look back at how the team has changed over time.
Create a retrospective
- Open your project and choose Retro in the sidebar.
- Click New Retro (or Create Retro if there are none yet).
- Choose the Sprint. Only active and completed sprints are listed, so you'll need to have started at least one sprint first.
- Fill in any of the three fields:
- What went well?
- What could be improved?
- Action Items: concrete steps for the next sprint.
- Click Create Retrospective.
A sprint is required, and at least one of the three fields must have text.
Review past retros
Retros are listed newest first. Each card shows the sprint name, the date it was created, and the three columns side by side. Empty columns show "No entries".
Retros can't be edited after you save them. To correct one, delete it with the x on its card (confirm the prompt) and create it again. LocalPM doesn't stop you from creating more than one retro for the same sprint, so delete the old one if you're replacing it.
Running the meeting
LocalPM records the result; the conversation still happens with your team. A simple flow:
- Before the meeting, look at the sprint in Reports and read back through blockers on the Standup page.
- Collect "went well" and "to improve" points from everyone, and type them in as you go.
- Agree on two or three action items with an owner for each.
- At the next sprint planning, review the previous retro's action items first.
Because action items live only in this browser, it's worth copying them into your team's shared notes too. For more on making retros useful, read Running a sprint retrospective that produces actual action items and Building a retrospective cadence that teams actually value.
Last updated
Still need help?
Or browse more LocalPM articles, all help topics, or the blog.