Automatic Creation
When a release is marked as delivered, Sinra creates its retrospective automatically. You never need to create a retro manually or remember to set up a Miro board at the end of a release.
Four Feedback Categories
Each retrospective collects feedback in four structured columns:
| Category | What goes here |
|---|---|
| Good | What worked well this release |
| Bad | What did not work or caused friction |
| Improvements | Specific process changes to try next time |
| General | Anything else worth noting |
Any team member can add entries to any column. Each entry is attributed to its author.
Discussion on Retro Items
Each retro entry supports a comment thread. This allows the team to discuss a specific point without cluttering the main retrospective view. Use comments to dig into root causes on “Bad” items or refine “Improvement” proposals.
Retro vs Cycle
Retrospectives are tied to releases, not cycles. This is intentional: what you learn about a delivery is about the features you shipped, not about the time period you worked. A release may span multiple cycles, and the retrospective reflects the full delivery.
Browsing Past Retros
All retrospectives are available in the Retros list, linked to their release. This creates a searchable history of what your team has learned. New team members can read past retros to understand recurring patterns and previous decisions.