Analytics Dashboard

The Analytics Dashboard gives you a unified view of how your team is performing across sprints, how work flows through your process, and where bottlenecks are forming. Rather than pulling metrics together from multiple views, the dashboard aggregates sprint data, task completion rates, and individual contribution signals into a single, readable interface.

Accessing the Dashboard

You can reach the Analytics Dashboard from two places:

Sidebar navigation: Select System from the main navigation, then click Analytics.
Project view: Open any project, then click the Analytics tab in the project sidebar.

The project-scoped view shows data for that project only. The system-level view aggregates data across all projects in your company.

Note: Viewer-role members can see the dashboard but cannot interact with forecasting or export controls. Admin and Owner roles have full access.

Sprint Health Score

The Sprint Health Score is a 0–100 composite metric that reflects how well a sprint is progressing against its goals. It updates automatically as tasks are completed, blocked, or moved.

What It Measures

The score is derived from three weighted inputs:

Signal	Weight	What It Tracks
Task Completion Rate	50%	Ratio of completed tasks to total committed tasks
Velocity Consistency	30%	How closely current sprint velocity matches the team’s historical average
Blocker Count	20%	Number of tasks flagged as blocked relative to total sprint tasks

How to Read the Score

80–100: Sprint is healthy. Delivery is on track and blockers are minimal.
60–79: Moderate risk. Review blocked tasks and check whether story point estimates need adjustment.
40–59: At risk. Significant blockers or low completion rate suggest the sprint may not deliver its committed scope.
0–39: Critical. Immediate action is needed — consider descoping or escalating blockers.

Alerts

When the Sprint Health Score drops below 60, a yellow warning badge appears on the sprint header across all project views. A drop below 40 triggers a red alert badge. These alerts are visible to all project members, not just admins.

If you have Slack or Microsoft Teams connected, IntuitivePM can post sprint health alerts to a designated channel. Configure this under Settings > Integrations > Notifications.

Velocity Chart

The Velocity Chart shows story points completed per sprint as a bar chart, making it easy to see trends over time. Each bar represents one sprint.

Reading the Chart

Each sprint bar displays two values:

Estimated (lighter shade): The total story points committed to the sprint at planning time.
Actual (solid): The story points that were completed and moved to Done by the sprint end date.

The gap between estimated and actual tells you how accurately the team is scoping sprints. A persistent pattern of over-estimation suggests the team is consistently committing to more than it can deliver, which is a common input into capacity planning conversations.

Interpreting Trends

Consistent actuals close to estimated: The team has reliable velocity and estimation is well-calibrated.
Actuals consistently below estimated: Sprint scope is being over-committed. Consider reducing capacity by 10–15% in the next sprint plan.
Actuals occasionally spiking above estimated: Scope was added mid-sprint. Check whether unplanned work is being absorbed without a corresponding commitment reduction.

Hover over any bar to see the sprint name, date range, and exact story point values.

Flow Metrics

Flow metrics measure how work moves through your process, independent of story points. They complement velocity by showing whether the system itself is efficient, not just whether the team is busy.

The Flow tab includes cumulative flow data by workflow status. Use the date range controls to inspect bottlenecks over time. If your workspace contains older project identifiers, IntuitivePM still calculates the chart from task history in the main application database so the tab remains usable.

Lead Time

Lead time is the elapsed time between when a task is created and when it is marked Done. It measures the full lifecycle of work, including time spent waiting in the backlog before a sprint picks it up.

A high lead time often signals backlog prioritization problems — work is being created but sitting unactioned for extended periods.

Cycle Time

Cycle time is the elapsed time between when a task moves to In Progress and when it reaches Done. It measures active execution time only, excluding backlog wait.

High cycle time relative to lead time indicates tasks are being started but taking longer than expected to complete. Common causes include unclear requirements, external dependencies, or tasks that are too large to finish in a single sprint.

Throughput

Throughput is the number of tasks completed per time unit (displayed as tasks per week by default). It is a raw count rather than a story-point measure, making it useful for tracking steady-state output regardless of estimation accuracy.

Tip: Use throughput alongside velocity. A team with high velocity but low throughput may be completing large, heavily-estimated tasks while a long tail of smaller items sits unfinished.

All three flow metrics are displayed as trend lines in the Flow tab of the Analytics Dashboard, with a 30-day rolling window by default. Use the date range picker to adjust the window.

Team Analytics

The Team tab breaks analytics down by individual contributor, giving leads visibility into workload distribution and contribution patterns.

Per-Member Contribution View

Each team member listed in the project appears as a row showing:

Tasks assigned: Total tasks currently assigned to them, across all sprints.
Tasks completed this sprint: Count of Done tasks attributed to them in the active sprint.
Average story points per sprint: Their personal velocity average over the last 5 sprints.
Current workload: A capacity indicator showing assigned story points relative to their historical sprint average.

How Assignment Data Feeds Analytics

When a task is assigned to a member and subsequently completed, IntuitivePM attributes that completion to the assignee. If a task is reassigned mid-sprint, credit goes to whoever was assigned at the time it was moved to Done.

Note: Unassigned tasks that are completed still count toward sprint-level metrics (Sprint Health Score, velocity) but do not appear in any individual member’s contribution row.

Forecasting

The Forecast section uses historical velocity to project how much work the team is likely to complete in future sprints. This is intended to help with roadmap planning and stakeholder communication, not as a hard commitment tool.

How It Works

IntuitivePM calculates a rolling velocity average over the last 5 completed sprints. When a sprint has fewer than 5 predecessors, it uses whatever historical data is available. The forecast shows a confidence range — a lower and upper bound — rather than a single number.

The confidence range narrows as velocity becomes more consistent. A team that has delivered between 40 and 45 story points for five straight sprints will show a tight range (e.g., 41–44). A team with high variance (30 points one sprint, 55 the next) will show a wider range (e.g., 28–58).

Reading the Forecast

The forecast panel shows:

Expected delivery: The midpoint of the confidence range for the next sprint.
Lower bound: The pessimistic estimate based on below-average historical sprints.
Upper bound: The optimistic estimate based on above-average historical sprints.
Backlog burn-down projection: An estimate of how many sprints it will take to clear your current backlog at the projected velocity, displayed as a date range.

Tip: Share the backlog burn-down projection with stakeholders as a range, not a single date. The confidence range is there precisely because software delivery has variance — committing to a single date based on velocity alone ignores that reality.

To share the current Analytics Dashboard view with someone who has access to the project:

Click the Share button in the top-right corner of the dashboard.
Copy the generated link. The link preserves your current date range, selected tab, and any filters you have applied.
Paste the link into Slack, Teams, or any other channel.

Recipients must be logged in and have at least Viewer access to the project to view the dashboard. The link does not grant access to anyone who lacks an existing invitation.

Exporting Data

Most chart panels include an Export option accessible from the panel’s overflow menu (three-dot icon in the top-right corner of each panel):

CSV: Exports the underlying data table for the selected metric and date range. Suitable for importing into spreadsheet tools.
JSON: Exports a structured JSON payload. Useful for feeding data into external reporting or business intelligence tools.

For API-based access to analytics data, refer to the API Endpoints reference.