The Kendis Analytics Dashboard provides a comprehensive, single-pane-of-glass view of your Solution Train's execution health. It aggregates data from the multiple connected PI Boards and transforms it into actionable, real-time insights, enabling Solution Train Engineers (STEs) and Program Managers to track progress, monitor scope changes, and assess predictability across the entire Solution Train.
This dashboard supports continuous tracking and dependency management throughout the execution of the Solution Increment, allowing STEs and Program Managers to make real-time decisions that optimize delivery flow and manage risks.
Key Benefits of the Analytics Dashboard (Solution Train Level)
Benefit | Description | Contextual Impact |
Real-Time Progress Visibility | See the completion status of Features, Stories, and Story Points across the entire Solution Train, aggregated from all underlying PI Boards. | Enables timely intervention by the STE or Program Manager to address systemic bottlenecks or slippage across multiple Agile Release Trains (ARTs) and manage cross-board dependencies. |
Scope Change Monitoring | Instantly track all Feature and Story additions and removals that occur post-PI planning across all managed PIs. | Provides objective data on "scope creep" and helps management understand the true cost of mid-PI changes, allowing for schedule adjustments to maintain viability. |
Predictability Analysis | The Story Points Burn-Down Chart compares the Plan (Ideal) line with the Actual execution line across the Solution Trainβs timeline. | Allows the Solution Train to gauge its ability to meet commitments and provides forward-looking insight into potential delivery issues. |
Team Load vs. Capacity | Visualize the allocated work (Load) against the available work effort (Capacity) for each Sprint/Iteration across all ARTs. | Helps identify persistent over- or under-committed ARTs and ensures a balanced workload for optimized delivery flow. |
Unplanned Work Insight | Clearly differentiates between committed work (planned during PI Planning) and unplanned work accepted during the execution phase. | Offers a true picture of operational efficiency and helps maintain focus on committed Solution-level items. |
Detailed Navigation and Functionality Guide
The Analytics dashboard is accessed directly from your active Solution Board and is divided into several key sections for easy consumption of Solution Train health metrics.
1. Accessing and Updating the Dashboard
The Analytics feature is available from the main Solution Board view.
Navigation Path:
From your active Solution Board locate the More dropdown button.
Click the More dropdown button.
In the menu that appears, click the Analytics option, which is typically the first item.
Once on the Analytics screen, you will see three main tabs: Dependency Tracking, Analytics, and Objectives. Ensure the Analytics tab is selected to view the progress metrics.
Updating the Data:
You can manually refresh the metrics to the latest data from your connected ALM tools.
Click the bright Update Analytics button (colored green in the screenshots) located in the top-right corner. The last generation time is displayed immediately to the left of this button.
2. Overall Solution Progress Tracking
Standard Status Color Coding
Across the entire Analytics Dashboard (in charts, tables, and modal views), work item status is consistently represented by three colored dots:
Orange (π΄): To Do / Remaining Work
Blue (π΅): In Progress
Green (π’): Done / Completed Work
2.1 Progress Bars (By Features, Stories, and Story Points)
These horizontal bars show the completed work percentage for the Solution Train.
View Toggle: Each bar section (Features, Stories, Story Points) has a toggle switch labeled All and Planned.
All (Default): Shows progress against all work items currently on the Solution Board, including scope added post-planning.
Planned: Shows progress only against the work items that were committed during the original PI Planning session.
Breakdown: Below the overall percentage, the progress is broken down by the individual Teams/ARTs contributing to the Solution Train (e.g., Web Bookstore - Q4 PI4, Mobile Bookstore - PI#5).
2.2 Program Progress Donut Charts
Located in the Sprint by Sprint View for Programs section, these charts visualize the aggregated work status from all connected PIs.
Note on Navigation: The Sprint by Sprint View for Programs section is collapsible by default. To view the individual charts for each Program Board, click the header of the respective Program Board (e.g., Web Bookstore - Q4 PI4) to expand the section.
Chart Group | Metric Measured | Key Insight |
All Stories Progress | Tracks all Stories currently associated with the Solution Train, broken down By # of Stories and By Story Points. | Provides the current snapshot of total work status, including unplanned work. |
Planned Stories Progress | Tracks only the Stories committed during PI Planning, broken down By # of Stories and By Story Points. | Provides a purer measure of execution against the initial PI commitment. |
Visual Cues: | Work status is color-coded: To Do (Orange), In Progress (Blue), and Done (Green). |
|
2.3 Portfolio Epic Progress (Drill-Down Detail)
This donut chart offers a high-level status view of the largest Solution Train initiatives (Epics/Features) and provides a crucial drill-down function for detailed analysis.
Metric Selector: Use the dropdown menu above the chart to choose the grouping metric:
Epic Status (default view, often the highest-level grouping).
Feature Status
Story Points (Recommended for effort-based progress tracking).
Progress Visualization & Interaction: The chart center shows the overall percentage complete (e.g., 11% Done). When you hover over a segment (like the To Do segment), the exact count appears (e.g., To Do: 59).
Drill-Down Modal: Clicking on any segment of the donut chart (To Do, In Progress, or Done) will open a comprehensive modal window, titled Portfolio Epic Progress - by Status.
2.4 Modal Analysis: Portfolio Epic Progress Detail
The modal details the work items contributing to the selected status segment, organized to show accountability across the Solution Train.
Column | Description | Key Insight |
Details | Lists the work item ID and name (e.g., '42 Search Frontend'). This information is initially grouped by Program Board/ART (e.g., 'Mobile Bookstore - PI#5 (4)'). | Shows exactly which Features/Epics are in the selected status (e.g., 'To Do'), and which ART owns them. |
Status | The current status of the work item (e.g., 'New', '-'). | Confirms the ALM status, related to the segment clicked. |
Team | The specific team responsible for delivering the work item. | Helps identify specific delivery teams within the ART. |
Sprint | The scheduled Sprint(s) for the work item. | Shows the planned delivery timeline. |
Board | The specific Program Board/ART where the work item is currently being tracked. | Crucial for identifying the source of the work and which board needs follow-up. |
Exporting the Chart Visual
All charts on the Analytics dashboard can be easily exported for inclusion in presentations or reports.
Accessing the Export Menu: Locate the small burger menu icon (three horizontal lines) in the top-right corner of the chart panel. Click this icon to open the export options.
Available Formats: A dropdown menu will appear offering several download options:
Print chart (For direct printing)
Download PNG image
Download JPEG image
Download PDF document
Download SVG vector image
3. Velocity and Predictability Analysis
3.1 Story Points Burn-Down Chart (Interactive Analysis)
This chart compares planned versus actual effort (Story Points) remaining over the Solution Train's timeline.
X-Axis: Represents the PI duration, labeled by individual Sprints/Iterations.
Y-Axis: Represents the Story Points Burn-Down (work remaining).
Plan Line (Orange): The straight, ideal line showing the target rate of progress.
Actual Line (Teal/Green): The line showing the real-time work remaining.
Interaction: If the Actual Line runs above the Plan Line, the Solution Train is behind schedule. You can hover over any point on the lines to see the precise remaining story point value for that specific iteration (e.g., hovering over the Actual line shows Plan 385 remaining at Iteration 2).
Customizing the Chart Data (Program Board Filter)
You can filter the burn-down data to focus on the performance of specific contributing ARTs or Program Boards:
Click the dropdown menu located at the top of the Story Points panel (the label lists all included Program Boards, e.g., Web Bookstore - Q4 PI4, Mobile Bookstore - PI#5, UX Team...).
A list will appear showing all connected Program Boards/ARTs with checkboxes.
Deselect the checkboxes next to any Program Board you wish to temporarily exclude from the burn-down calculation.
Click Done to update the chart, which will now display the burn-down lines based only on the filtered set of Program Boards.
Exporting the Chart Visual
The Story Points Burn-Down Chart also supports the standard chart export options for reporting:
Accessing the Export Menu: Locate the small burger menu icon (three horizontal lines) in the top-right corner of the chart panel.
Available Formats: A dropdown menu will appear offering the standard options, including Download PNG image and Download SVG vector image.
4. PI Planning Variations & Scope Changes
This tabular section provides objective data on changes to the collective PI plans post-commitment.
Category | Field | Description | Click-Through (Interactive Detail) |
Scope Changes | Features Added/Removed | Counts of Features added to or removed from the scope since planning across all PIs. | Clicking the numeric value (e.g., 110) opens a modal showing the list of affected Features/Stories, grouped by the contributing Program Board, along with Status, Team, Sprint, and Board details. |
| Stories Added/Removed | Counts of Stories added to or removed from the scope since planning. | Clicking the numeric value opens a modal showing the list of affected Stories, grouped by the contributing Program Board, along with Status, Team, Sprint, and Board details. |
| Added Story Points | Total estimated effort of all new work added since the plan was finalized. | Not typically clickable, as it is a summed value. |
Feature Delivery Variations | Feature changed their delivery sprint after Previous State | Number of Features that have been moved to a different Sprint later in the PI. | Clicking the numeric value opens a modal showing the list of affected Features, grouped by the contributing Program Board, along with relevant details. |
Sprint Planning Variations | Story changed their sprint after Previous State | Number of Stories that have been moved (typically to a later Sprint or a spillover/IP iteration). | Clicking the numeric value opens a modal showing the list of affected Stories, grouped by the contributing Program Board, along with relevant details. |
5. Capacity and Load Analysis
This section offers different views for analyzing work allocation against team capacity, aggregated from the connected PI boards.
5.1 Iteration Capacity vs. Load Bar Chart
This visual provides a powerful, Sprint-by-Sprint comparison of resource planning across the entire Solution Train.
X-Axis: Shows individual Sprints/Iterations (e.g., Iteration 1, Iteration 2).
Legend:
Capacity (Orange Bar): The available effort the ARTs can handle.
Load (Purple Bar): The total estimated work (Story Points) planned for the iteration.
Done Story Points (Green Bar): The actual effort completed to date in that iteration.
Key Insight: Comparing the Capacity and Load bars instantly reveals if an iteration is overloaded across the Solution Train (Load is significantly higher than Capacity, e.g., Iteration 1).
5.2 Solution Board: Sprint by Sprint View (Program Summary)
This table summarizes the overall metrics by Sprint across all connected PIs at the Solution Train level.
Column | Metric Measured | Context | Click-Through (Interactive Detail) |
Feature | Total Features planned for the Sprint. | The associated bubbles show the status breakdown using the standard color coding (π΄ To Do, π΅ In Progress, π’ Done). | Clicking the numeric value (e.g., 14) opens a modal showing the detailed list of those Features, grouped by Program Board. |
Stories | Total Stories planned for the Sprint. | The associated bubbles show the status breakdown using the standard color coding (π΄ To Do, π΅ In Progress, π’ Done). | Clicking the numeric value (e.g., 43) opens a modal showing the detailed list of those Stories, grouped by Program Board. |
Story Points / Load | The total committed effort for the Sprint. | The associated bubbles show the status breakdown of the Story Points effort: To Do (π΄), In Progress (π΅), and Done (π’). | Not clickable, as it typically represents a total estimated effort value. |
Capacity(C) | The summed capacity of all teams/ARTs for that Sprint. |
| Not clickable. |
C - L | Capacity Minus Load: The variance between team capacity and planned work (Load). Negative values indicate overload (e.g., Sprint 1 is -100.00). |
| Not clickable. |
5.3 Solution Board: Session by Session View (ART/Program Board Details)
This table is critical for evaluating the predictability and planning success of the individual Program Boards that contribute to the Solution Train.
Rows: Each row represents a specific Program Board/ART (e.g., Web Bookstore - Q4 PI4, UX Team, Marketing Team).
Features: Total Features planned for the ART/Program Board. The associated bubbles show the status breakdown using the standard color coding (π΄ To Do, π΅ In Progress, π’ Done).
Stories: Total Stories planned for the ART/Program Board. The associated bubbles show the status breakdown using the standard color coding (π΄ To Do, π΅ In Progress, π’ Done).
Story Points/Load: The total committed effort for the ART/Program Board. The associated bubbles show the status breakdown of the Story Points effort: To Do (π΄), In Progress (π΅), and Done (π’).
Capacity(C): Shows the specific capacity entered for that Program Board's PI.
Planned Sum: The row shows the aggregated total Features (76), Stories (130), and Load (770.00) that were committed during PI Planning for all ARTs/Teams in the Solution Train.
Unplanned Sum: The row shows the aggregated total work items and effort (Story Points) that were added after the initial PI commitment across the Solution Train.
C-L: This column shows the Program Board's remaining capacity across the PI. A negative number here means the ART is currently holding more estimated work (Planned + Unplanned) than their stated capacity allows, indicating a high risk of slippage.
6. Exiting the Analytics Dashboard
Once your analysis is complete, you have three options for navigating away from the Analytics screen:
Switch to Dependencies: Click the Dependency Tracking tab at the top left of the screen to move to the dedicated view for managing cross-board dependencies.
Switch to Objectives: Click the Objectives tab at the top to review and manage Solution Train Objectives and Key Results (OKRs).
Return to Solution Board: Click the "X" (Close) icon in the top right corner of the screen to return directly to the main Solution Board view.
