This guide introduces the new Analytics experience in Kendis. Analytics helps you understand delivery progress across features, iterations, and teams. It provides charts, summaries, and insights that make it easier to track what is planned, what is delivered, and where risks exist.

Use this guide to learn:

Analytics is a reporting workspace that shows delivery progress in one place. It helps you track planned versus delivered work, monitor progress across sprints and increments.

You can review feature completion, evaluate team performance, and identify delivery risks early without switching between multiple boards.

Analytics allows you to switch between Burndown and Burnup views. These charts show how work progresses across iterations.

Burndown chart

Burnup chart

In the Burnup chart, you may see:

Planned line → total planned work.

Actual line → completed work.

Remaining line → work left.

Current iteration highlight → where you are now.

Analytics is useful for:

To open Analytics:

Go to the program board or workspace you want to review.

Click Analytics in the top bar.

First-time use: The view initially opens in a blank state with the message: "Select a data source to view analytics." Select a Burndown Source from the controls bar to begin. Data loads automatically as soon as a valid source and context are selected.

You can customise what data is included in Analytics using the Settings icon in the toolbar. Click the settings icon to choose additional data sources for the charts.

You can select fields from:

These fields allow you to group and compare delivery data based on different properties such as card type, assignee, project, labels, or WSJF score.

After selecting the fields, click Done to apply the changes.

Analytics in Kendis provides two main views that help you understand delivery from different perspectives, Feature Analytics and Team Delivery.

Feature Analytics shows delivery progress based on features, scope, and iterations. Use this view to understand what was planned, what was delivered, and where the scope changed.

Filters and Controls: You can use the controls at the top to change what data you see. Available filters include burndown source, plan view, display, and settings.

Summary Cards: The summary cards show the current delivery status.

Burndown/Burnup Chart: The chart shows progress across iterations. They are helpful to make sure your delivery is on track.

Iteration Breakdown: The iteration table shows delivery per sprint.

Scope Changes: It shows the work added or removed after planning.

Feature Health Overview: This section shows feature status. You can also group by parent, objective, milestone, team, or label.

Needs Attention: This table lists features that are behind schedule.

Team Delivery shows progress based on teams instead of features. Use this view to check commitment reliability and team performance.

Filters/Controls: Team Delivery has quite different filters and controls available for more refined team-level analytics.

Summary Cards: The Decards show delivery numbers for teams.

Burndown/Burnup Chart: The chart shows delivery across teams. Useful to detect over-commitment.

Team Health Overview: This table shows performance for each team.

Delivery Gaps: Delivery Gaps shows teams behind commitments.

Scope Changes: This section shows scope changes by team.

Some views allow you to change how progress is calculated. You can switch between:

Switching the view changes how charts and numbers are calculated.

You can also change how work is measured.

Analytics can show progress using:

You can switch between these modes using the display controls.

This guide introduced the Enhanced Burndown Analytics workspace and explained how to navigate between Feature Analytics and Team Delivery. In the next guides, we will explore each analytics view in detail, including how to interpret charts, understand delivery metrics, and analyse execution performance.