Team Analytics
Overview
Section titled “Overview”Team Analytics gives you MVP-scoped charts for team delivery health: throughput over time, open versus closed work, and basic per-project breakdowns. It is deliberately simple, a weekly-review tool rather than a full business-intelligence suite.
The charts read from the same sprint and task data everyone already updates on the sprint board and Task Explorer, so there is no separate data entry step. Accuracy here depends entirely on how consistently the team updates status elsewhere.
Deeper analytics, including AI-generated reports, custom dashboards, and portfolio health scoring, sit outside MVP scope and are reached from a different, more advanced surface once your organization has them enabled.
What you can do here
Section titled “What you can do here”- View throughput trends over a selected date range.
- Compare open versus closed work for a project or the whole team.
- Filter by project or team to focus on a specific slice.
- Export or screenshot a chart for a leadership update.
When to use
Section titled “When to use”- Weekly team reviews without opening an advanced analytics suite.
- Quick health checks before a stakeholder sync.
- Spotting a stalled project before it becomes a bigger problem.
Prerequisites
Section titled “Prerequisites”- A signed-in member account with product access.
- At least one project with sprint or task history to chart.
Where to find it
Section titled “Where to find it”- Sidebar: Reports (Team Analytics)
- Direct route:
/reports
Step-by-step
Section titled “Step-by-step”- Open Reports / Team Analytics (
/reports). - Select a date range that matches the review you are preparing.
- Apply team or project filters to narrow the view.
- Read the throughput and open-versus-closed charts.
- Note any project that looks stalled or unusually behind.
- Export or screenshot a chart if you need to share it outside the app.
What success looks like
Section titled “What success looks like”- You can answer “how is the team doing” in one glance before a review.
- A stalled project surfaces here before it becomes a surprise later.
- Leadership updates use a real chart instead of an anecdotal summary.
Tips & best practices
Section titled “Tips & best practices”- Check Team Analytics right before a weekly review, not just when something already feels wrong.
- Advanced AI reports may be plan-gated; this page always covers the MVP basics regardless of plan.
- Keep status updates accurate on the sprint board so these charts stay trustworthy.
Common mistakes
Section titled “Common mistakes”- Treating a chart as accurate when the underlying sprint board has stale, unmoved cards.
- Expecting AI-generated report narratives here; that is a separate, more advanced surface.
- Skipping a weekly look at this page and only noticing delivery problems once they are serious.