How do I organize and filter retrospectives for different teams?
Group boards by team association and use dashboard filters to maintain clean sprint histories across squads.
Problem This Solves
Group boards by team association and use dashboard filters to maintain clean sprint histories across squads.
When to Use This
Multiple teams or sprint boards created in your workspace.
Prerequisites
- Multiple teams or sprint boards created in your workspace.
Step-by-Step Instructions
- Associate Boards with Teams during Creation: When clicking
+ Create boardon your dashboard, select the target squad in the team association selector. - Filter Boards Directory: Navigate to
/dashboard/boards. Use the team filter dropdown menu to view only boards belonging to a specific engineering squad. - Prevent Cross-Team Clutter: Grouping boards by squad ensures sensitive team feedback or unrelated sprint action items do not distract adjacent product squads.
- Track Team-Specific Trends: In the
Trendstab (/dashboard/trends), generate AI trend analytics filtered by specific teams to track team sentiment across sprints. - Reopen Historical Sprints: Filter by closed or completed status to easily pull up previous sprint retrospectives for quarterly planning or audit reviews.
Expected Outcome
Your retrospective boards are structured cleanly by squad, making it effortless to track sprint progress and review history.
Troubleshooting & Realistic Tips
- Use clear sprint numbering in board titles (e.g. 'Sprint 24 — Payments') alongside team filters for seamless auditing.