The Program Board Analytics feature provides a comprehensive, multi-faceted view of your Program Increment (PI) execution, offering detailed metrics on progress, team performance, scope changes, and feature delivery across the entire program. It acts as the central hub for tracking key performance indicators after the PI planning phase is complete.
This analytical dashboard is designed to give Release Train Engineers (RTEs), Product Management, and all stakeholders the actionable data needed to assess the health of the PI in real time. By consolidating key metrics—from the overall PI Burndown status to granular details about individual team loads and feature completion—Analytics provides an unparalleled level of transparency into what was planned, what is being tracked, and how scope changes are impacting the final delivery. Whether you need to visualize the remaining work using the PI Burndown Chart, identify a team that is consistently under-committed, or pinpoint the source of feature delays, this feature offers five distinct, interlinked views to track and manage your PI execution effectively.
Key Benefits of Program Board Analytics
Benefit | Description |
Holistic Progress View | Visualizes the PI Burndown, showing Planned vs. Actual Story Points done across all teams and iterations. |
Scope Change Tracking | Clearly isolates and quantifies features, stories, and Story Points that were added, removed, or changed after the board moved into the tracking state. |
Granular Feature Breakdown | Provides an in-depth breakdown of each feature's progress, showing completion based on both Story Count and Story Points. |
Team Performance Analysis | Shows team-specific metrics, including Planned Load, Committed Load, Done Points, and Capacity for each iteration, identifying over-or under-planned teams. |
Customizable Calculations | Allows Super Admins to precisely define which Card Types, Statuses, and Issue Types should be included in the analytics calculations for both general progress and Objectives. |
Accessing and Navigating Program Board Analytics
The Analytics feature is accessed directly from your live Program Board.
Step-by-Step Navigation Guide
Access the Program Board: Navigate to your desired Program Board (e.g., PI#8 - Q1 2025 ).
Open the Menu: Locate and click the More menu dropdown, typically positioned on the top-right of the board, next to the Board Settings.
Launch Analytics: In the dropdown menu that appears, look under the menu section and click the Analytics icon (typically a red circle with a line graph inside).
Note: The Program Board must be in the Tracking board state to display execution analytics.
The Analytics dashboard will open in a new view, replacing the Program Board.
Navigate Sections: The analytics are organized into five key tabs located across the top ribbon:
Summary
Delivery By Features
Delivery By Teams
Delivery By Sprints
Progress By Team
Configuring Calculation Settings (Admin Only)
Before diving into the reports, it's crucial to understand how the metrics are calculated. These settings are configurable and determine what data is included in the charts and tables.
How to Adjust Calculation Filters
Open Settings: From any Analytics tab, click the Settings icon (a grey cog/gear icon) located in the top-right corner of the view. A Calculation Settings modal will open.
Configure Analytics (Burndown and Progress): The Analytics tab controls the criteria for general progress and burndown charts:
Card Type: Select the type of top-level item (e.g., Feature, (Global) Unprinted Stories) to base the calculation on. This is a multi-select dropdown, allowing you to choose multiple card types.
Features Status: Define which Feature statuses (e.g., New, To Do, Design, Requested, Approved, Accepted...) are considered for the calculations. This is a multi-select dropdown.
Features Issue Types: Define which Issue Types are counted within Features (e.g., Task, Bug, Code Review Request...). This is a multi-select dropdown.
Stories Status: Define which Story statuses are included. This is a multi-select dropdown.
Stories Issue Types: Define which Issue Types are counted within Stories. This is a multi-select dropdown.
Note: All of the status and issue type dropdowns support Check All and Uncheck All options for quick selection.
Configure Objectives (Objectives and Confidence Vote): Click the Objectives tab to set criteria for Objectives-related calculations, specifically affecting metrics like Business Value Achieved. This tab includes the following fields, all using multi-select dropdowns:
Card Type: Select the item type (e.g., Feature, Epic, (Global) Unprinted Stories) that will be linked to an Objective.
Features Status: Define which Feature statuses will count toward an Objective's completion (e.g., Done, Accepted).
Features Issue Types: Define which Issue Types within Features are relevant to the Objective calculation.
Stories Status: Define which Story statuses will contribute to Objective progress.
Stories Issue Types: Define which Issue Types within Stories are relevant.
Stories Planned: Define if only Planned, Unplanned, or both types of stories should be included when calculating progress against Objectives.
Note: Like the Analytics tab, all status and issue type dropdowns here support the Check All and Uncheck All options for efficiency.
Save Changes: Click the Save button (typically green) to apply the new filtering criteria to all reports.
Detailed Overview of Analytics Tabs
1. Summary
This section provides a high-level overview of the entire PI, focusing on the Burndown Chart and overall progress metrics.
PI Overview (by Sprint/Iteration): Located at the top, this area shows the key dates and metrics.
Context: The value shown in "Days Left" is based on business days, not calendar days.
Filtering: You can switch between viewing the overall PI or individual Sub-tracks (if configured).
PI Burndown Chart: Shows the planned (orange line) versus actual (green line) story points completed over the course of the PI's sprints. It shows progress based on "Cumulative Story Points" and can be viewed for the single PI or the entire track.
Interaction: The chart is interactive. Hover over data points to see specific details about planned, actual, and committed load for that sprint. You can also click on the legend items (e.g., Plan, Actual, Committed Load) located below the chart to show or hide the corresponding data lines.
PI Burndown Chart Legend Definitions
Legend Item | Color/Description | Meaning |
Plan | Typically Orange Line | Represents the ideal burndown path based on the initially planned load for the PI. If followed, the PI would finish on time. |
Actual | Typically Green Line | Represents the actual progress made in Story Points completed over time by all teams in the PI (a real-time snapshot). |
Committed Load | Typically Blue Line | Represents the total Story Points that teams have formally committed to complete during each sprint. |
(Tracking) Load | Typically Yellow/Light Brown Line | Represents the remaining work based on the current state of all stories in the PI, including all scope changes made during tracking. |
(Planning) Load | Typically Purple Line | Represents the total initial scope of work defined during the planning phase (before the board state changed to Tracking). This value is frozen and used as a reference point for scope changes. |
Capacity | Typically Teal/Light Green Line | Represents the total available capacity of all teams combined for each sprint in the PI. |
Progress and Risk Widgets
Prediction of Completion: This widget provides a forecasted completion date based on the current progress rate. The prediction is calculated by dividing the total remaining story points by the average story points completed per business day.
Features/Stories at Risk: This widget highlights items that are not tracking towards their target story points based on the current execution rate.
Progress by Card Type: This widget shows the percentage of completion based on the status (Done/category) of the items. You can toggle this view between Feature level and User Story level, and it includes non-feature work items like Bug and Project Activities.
Filtering: You can use the Select dropdown (which is a multi-select with Check All/Uncheck All options) to choose which sprints you want to include in the progress calculation.
Viewing: Use the radio buttons to toggle between viewing progress by Card Type Status or Linked Items Status.
Planned vs. Unplanned Status Table: Located on the right, this table provides a summary breakdown of work items by their planning status and current completion status:
Metric | To Do | In Progress | Done |
# of Unplanned Features | Count of unplanned features in this status. | Count of unplanned features in this status. | Count of unplanned features in this status. |
# of Planned Features | Count of planned features in this status. | Count of planned features in this status. | Count of planned features in this status. |
# of Planned Stories | Count of planned stories in this status. | Count of planned stories in this status. | Count of planned stories in this status. |
Story Points | Total story points in the To Do status. | Total story points in the In Progress status. | Total story points in the Done status. |
Key Metrics Table: Displays summarized data at the bottom, including (Planning) Load, (Tracking) Load, Committed Load, Done Points, and Capacity for each sprint.
2. Delivery By Features
This section focuses on the delivery status of individual features and the impact of scope changes.
Scope Changes Section: A key widget that shows the quantitative impact of scope changes since the board entered the tracking state:
Unplanned (Not in any sprint): Shows features, stories, and estimates that remain in the backlog.
Context: Kendis treats stories that are not mapped to a sprint on the Program Board as "Unplanned for this PI", even if they are planned in a linked external tool (like Jira/ADO).
Interaction: Clicking on the Features, Stories, or Estimate (Story Points) count in the Unplanned (Not in any sprint) widget will open a modal list showing the relevant unplanned items.
Scope Changes: This number represents the difference between the (Planning) Load and (Tracking) Load. It shows the count and percentage of features, stories, and story points that were Added or Removed after the board state transition from Planning to Tracking.
Interaction: Clicking on the Features, Stories, or Estimate (Story Points) count in the Scope Changes widget will open a modal list showing the relevant added or removed items.
Feature Delivery Variations: Highlights the percentage of features and stories whose sprint was changed after initial planning. This is also referred to as Sprint Planning Variations.
Interaction: Clicking on the count for Feature Delivery Variations or Sprint Planning Variations will open a modal list showing the affected features and stories.
Feature List Filtering: Use the filtering options above the features list to narrow down the results:
Sprint Filter: You may filter to a specific sprint to narrow down the results to only that period's scope and progress.
View Filter: Allows you to view the features that were added or removed from the board during the tracking state.
Planned Features List: A detailed table of all planned features:
Progress %: Shows two distinct progress bars for each feature:
By Story: A teal progress bar based on the count of completed stories.
By Estimate: A progress bar based on the Story Points completed.
Story Breakdown & Estimate Breakdown: These sections provide detailed metrics for each team working on the feature (e.g., TVN, TE).
The progress for stories is calculated based on the following standard state mappings:
Kendis State | External Tool (e.g., ADO) State |
To Do | New-Planning (Proposed) |
In Progress | In Progress-Validation |
Done | Closed |
Misc | Removed |
Shows the count/points of Completed (Done), In Progress, To Do, and Spillover items.
Context: Spillover refers to stories that were incomplete and moved to another sprint upon sprint closure.
3. Delivery By Teams
This section provides a team-centric view of execution and performance, highlighting planned versus actual delivery.
Team Performance Summary: The top widgets show each team's progress based on multiple criteria (e.g., progress by feature, stories completed, features done by stories/estimate).
Feature Completion Logic: For features being worked on by two or more teams, the percentage of completion is shown for each team based on the stories assigned to them. True progress of completion is only achieved when all stories related to a feature are done, regardless of the actual feature status in the external tool.
Interaction: You can toggle the completion metrics between By Estimate and By Count. You can also click on the bars in the charts to view the work items and details (Parent ID, details, status, estimate, team, sprint).
Team Metrics Table (Planned Work vs. Load): This table is helpful during the PI Planning Review to show which teams have under- or over-planned their loads:
Feature, Stories, Story Points: Reflects the total planned work for the team.
Capacity (C), Load (L), and Capacity - Load (C - L): The Capacity - Load column quickly identifies over-planning (negative values) or under-planning (positive values).
Charts by Team: Displays individual bar charts for each team, offering a visual summary of their sprint work.
Load Definitions in Charts:
Previous (Planning) Load: The total Story Points for all stories in the Sprint at the end of the Planning (before the board state changed to Tracking). This is a frozen reference load.
Current Load: The total Story Points for all stories currently in the Sprint. If the board state is Tracking, the Current Load is equivalent to the (Tracking) Load. Any stories added after the Sprint started are included here but are not part of the Committed Load.
Committed Load: The total Story Points for all stories included in the Sprint at the "Start of the Sprint."
Context: Committed Load is the story points each team committed to at the beginning of the sprint. Comparing this to Done Story Points helps understand execution predictability and identify work that was not completed during the sprint.
Interaction: All the graphs in this section are clickable to help you understand the contents behind the numbers.
4. Delivery By Iterations
This section breaks down progress based purely on the sprint level. This view is often referred to as the Program Report.
Report Management: Located at the top right of the report, you can manage the report view:
Share Link: Generate a shareable link to the report (requires log in to Kendis to view).
View Older Versions: Access previous snapshots of the report. This is particularly useful as the Sprint Report provides a snapshot of the PI's status at the end of a sprint (which is a More Qualitative Report than the general analytics).
Leave Notes: Add contextual notes to the Sprint report.
Sprint Reports List: Provides a list of all sprints in the PI. You can click View Report next to any sprint to open a full, detailed Sprint Report. For more information, see How Sprint Reports Work.
Sprint Data Table: Shows the aggregated data per sprint:
Scope Change vs Sprint Start: Reflects features/stories added after the board state transitioned from Planning to Tracking, specifically tied to the start of a given sprint.
Scope Change vs Planning: Reflects features/stories added after the board state transitioned from Planning to Tracking, specifically tied to the initial Planning phase.
Features, Stories, Story Points, Capacity (C), Load (L), and Capacity - Load (C - L).
Note: The Capacity - Load column highlights sprint-level over-commitment (negative red values) or under-commitment (positive values).
Interaction: All numbers shown in blue in this table are double-clickable to view the underlying work items and details (Parent ID, details, status, estimate, team, sprint).
5. Progress By Team
This section provides a final comprehensive overview of deliveries by teams, focusing on the impact of scope changes, load comparisons, and completion metrics.
Team Filter Dropdown: At the top of the section, a dropdown menu allows you to select a specific team to isolate their data and view a team-level graph. By default, this view shows aggregated data for all teams or the overall sub-track.
View by Subtrack: If your Program Board uses Sub-tracks, you can switch sub-tracks here to narrow the scope of the graphs.
Overview Widgets: Provides visual summaries of delivery by teams, focusing on Stories Completed and Features Done by Stories/Estimate.
Plan vs. Actual Table (Scope Change Impact): The table at the bottom shows the planned, spillover, added, and removed stories/story points for each team, providing a clear visual representation of how the initial plan was affected during the tracking state.
This table is key for reviewing performance:
Plan: The initial load assigned to the team during planning.
Spillover: Stories incomplete at sprint closure and moved to a future sprint.
Added: Stories added to the team's scope after the PI entered the tracking state.
Removed: Stories removed from the team's scope after the PI entered the tracking state.
Context: This section shows what was planned, the current situation in the tracking state, and how scope changes impacted the delivery of each team.
Interaction: All the graphs in this section are clickable to help you understand the contents behind the numbers.