Skip to main content

Feature Analytics: Tracking Feature Delivery Progress

Feature Analytics helps you track feature-level delivery in Kendis. Learn how to read burndown charts, iteration breakdowns, scope changes, and health indicators.

Written by Kendis Team
Updated over a week ago

Feature Analytics helps you understand how features are progressing across sprints and increments. In this guide, you will learn how to read the charts, tables, and indicators available in the Feature Analytics view.

It is the main workspace for visualising feature delivery. It helps you see:

  • What was planned.

  • What has been delivered.

  • What scope changed.

  • Which features are behind plan.

  • How delivery is progressing over time.

Accessing Feature Analytics

  • Open your board in Kendis.

  • Click Analytics in the More menu.

  • Select Feature Analytics.

Feature Analytics opens with charts, summary cards, and tables showing delivery progress. If no data appears, select a Burndown Source first.

Feature Analytics Layout Overview

Feature Analytics contains the following sections:

  1. Burndown Source selector.

  2. Plan View and Display options.

  3. Summary cards.

  4. Burndown / Burnup chart.

  5. Iteration Breakdown Table.

  6. Scope Changes panel.

  7. Feature Health Overview.

  8. Needs Attention list.

Each section helps you understand delivery from a different perspective.

Selecting Burndown Source

Use the dropdown on the left to select what data to analyse.

You can view analytics by:

Option

What it loads

Customise Values...

Opens the Configuration Panel to enable additional data sources.

All Features

Every feature on the board.

By Epic, By Capability, By Theme, By Portfolio Epic, etc.

Features grouped by a specific parent type. A second dropdown appears to select a specific parent item.

By [field name]

Features grouped by ALM-synced fields enabled in your board settings (e.g., Jira custom fields). These appear only if enabled in the Config Panel.

By [field name]

Features grouped by Kendis-only custom fields. These appear only if enabled in the Config Panel.

Top 10 by WSJF

The 10 highest-WSJF-scored features

WSJF Comparison Criteria

Features grouped by WSJF comparison criteria. A second dropdown appears to select a criteria.

By Objectives

Features linked to objectives. Reveals Objective Group and Objective dropdowns.

By Milestone

Features linked to milestones. A dropdown appears with "All Milestones" or individual milestones.

By Risk

Features associated with risks. A dropdown appears with "All Risks" or individual risks.

Individual Feature

Enables a search box to find and select specific features by name or ID.

By Parent

Opens a multi-select parent picker panel for selecting multiple parent items at once.

By Shared Filter

Features from a saved shared filter. A dropdown appears to choose a filter.

Selecting a source updates all charts and tables. Burndown source helps you stay focused on a specific group of features.

Plan View

Plan View controls how progress is calculated.

Option

Description

PI Plan

Uses the PI planning baseline as the reference for planned scope. Scope changes are calculated against the original PI plan state.

Sprint Delivery

Uses sprint-start baselines as the reference. Scope changes are calculated per sprint against each sprint's start-of-sprint snapshot. Shows carry-over row and sprint-level baseline indicators.

Display Mode

Display mode controls how work is measured in charts, summary cards, and tables.

You can choose whether progress should be calculated using story points or the number of items.

Option

Unit

What it shows

By Estimate

Story Points (SP)

All metrics in story points

By Story

Stories

All metrics as story counts

By Count

Features

All metrics as feature counts (completed/done)

Changing the display mode updates all charts, summary cards, and iteration calculations.

Summary Cards

Summary cards show a quick snapshot of the current delivery status based on the selected filters, plan view, and display mode. They help you understand overall progress before moving into the chart and detailed tables.

Planned Scope: Shows the total amount of work planned for the selected features. It acts as the baseline for measuring delivery progress.

Delivered: Shows how much of the planned work has been completed so far.

Remaining: Shows how much planned work is still left to finish.

Unplanned: Shows work that was added after planning and is not yet allocated in the original scope.

These cards update automatically when you change the burndown source, plan view, or display mode.

Burndown/Burnup Chart

The Burndown / Burnup chart shows how delivery progresses over time based on the selected plan view, burndown source, and display mode.

It helps you understand whether work is being completed as planned and if the scope has changed during execution.

You can switch between two chart types:

Burndown Chart

The Burndown chart shows how the remaining work decreases over iterations. If the remaining line goes down steadily, delivery is on track. If the line stays flat or goes up, work may not be completed as planned, or the scope may have increased.

Burnup Chart

The Burnup chart shows how completed work increases over time compared to the total planned scope.

Common lines in the chart:

  • Planned / Scope line → total planned work.

  • Delivered / Actual line → completed work.

  • Remaining line → work left to finish.

  • Adjusted scope → updated scope after changes.

  • Current iteration highlight → where you are now.

If the scope line moves up, new work was added. If the delivered line stays below scope, delivery may be behind.

Iteration Breakdown

This is a horizontal data table with one column per sprint plus a Total column on the right. The current sprint column is highlighted in light green.

Row

Description

Planned SP / Planned Stories / Delivery Plan / Completing

Scope planned/allocated for each sprint (label changes by mode).

Delivered SP / Done Stories / Done

Scope delivered in each sprint.

Gap (P - D)

The difference between planned and delivered. Red if positive (behind), green if negative (ahead).

Planned %

Planned as a percentage of the total scope.

Delivered %

Delivered as a percentage of the total scope.

Carry-over

Stories carried forward from the previous sprint. Amber text when > 0.

Scope Change

Net scope change per sprint. Red if positive (scope added), green if negative (scope removed). An asterisk (*) appears next to sprints that were not started.

Cum. Planned / Cum. Delivery

Cumulative planned across sprints.

Cum. Delivered / Cum. Done

Cumulative delivered across sprints.

Metric column: Sticky on the left side so it remains visible when scrolling horizontally.

Scope Changes

The Scope Changes section shows work that was added or removed after planning.

At the top of the panel, you can see a summary of scope updates:

SP added → Total story points added after planning.

SP removed → Total story points removed.

Net change → Final difference in scope.

This summary helps you quickly understand whether the scope increased or decreased.

Feature Health

Feature Health shows the status of all features.

Below the bar, a legend shows the count for each status. A tab bar that provides different breakdown views of the feature set:

Tab

Description

Summary

Table showing each parent type with item count, feature count, total scope, delivered scope, and progress bar. Click a row to switch to that type's tab.

[Type] tabs (Epic, Capability, etc.)

One tab per parent type. Table shows individual parents with feature count, scope, delivered, and progress. Click a row to drill into that parent's individual burndown.

[Custom field] tabs

One tab per enabled custom group-by field. Shows values for that field with feature count, scope, delivered, unplanned, and progress. Click a row to drill into that group's burndown.

WSJF Criteria

Table of WSJF comparison criteria with feature count, scope, delivered, unplanned, avg WSJF score, and progress. Click a row to drill into that criteria's burndown.

Needs Attention

Needs Attention shows features behind plan.

Each item shows:

  • Feature name.

  • Team.

  • Total SP.

  • Gap.

  • Progress %.

Use this section to identify:

Features at risk.

Features delayed.

Features needing discussion.

Click the feature to open its burndown.

Recommended Approach for Feature Analytics

  • Start with Summary Cards.

  • Review the Burndown / Burnup Chart.

  • Check the Iteration Breakdown.

  • Look at Scope Changes.

  • Review Feature Health Overview.

  • Check Needs Attention.

Following this flow gives you a clear and complete picture of delivery progress and helps you quickly understand where action is needed.

In the next guide, we will explore Team Delivery, which shows progress based on teams instead of features.

Did this answer your question?