Team Delivery helps you understand how teams are performing across sprints and increments. In this guide, you will learn how to read the charts, tables, and indicators available in the Team Delivery view.
Team Delivery helps you answer:
How much work did each team commit?
How much work was actually delivered?
Which teams are behind plan?
Which teams met their commitments?
How reliable are the teams across iterations?
This view combines iteration commitments, delivery data, and team performance metrics in one place.
Opening Team Delivery
Open your board in Kendis.
Click Analytics from the More menu.
Once inside the Analytics workspace, use the toggle at the top to switch to Team Delivery.
The Team Delivery view opens with filters, summary cards, charts, and team performance tables. If no data appears, select a Delivery Source and Iterations first.
Team Delivery Layout
Team Delivery view is organised into multiple areas that show delivery progress, commitments, and team performance.
You will see:
Delivery Source selector.
Iteration selector.
Plan / Delivery mode controls.
Display options.
Summary cards.
Burndown / Burnup chart.
Team Health Overview.
Delivery Gaps.
Top Performers.
These sections work together to give a complete view of how teams are performing across iterations.
Selecting Delivery Source
Use the dropdown on the left to select which teams to analyse.
Team filter dropdown:
Click to expand a dropdown with all teams on the board.
All Teams checkbox at the top toggles all teams on/off.
Individual team checkboxes allow multi-select.
Click outside the dropdown to close it.
Sprint filter dropdown:
Same pattern as team filter.
All Sprints checkbox at the top.
Individual sprint checkboxes.
Note: Selecting a source updates all charts and tables. Delivery source helps you focus on a specific team or group of teams.
View Toggle
You can switch between different modes to analyse commitments, scope changes, and delivery progress from different perspectives. Use the Sprint Detail View toggle to change how sprint data is compared, and use the Unit toggle to change how work is measured.
Sprint Detail View toggle
Option | Description |
Sprint Commitments | Compares increment plan vs sprint commitment vs delivery. Shows Increment Plan, Sprint Committed, Delivered, Carry-in, Delivery %. |
Sprint Delivery | Compares sprint commitment vs current in-sprint scope vs delivery. Shows Sprint Committed, Current in Sprint, Delivered, Scope Added, Scope Removed, Delivery %. |
Unit toggle
Option | Description |
By SP | All values in Story Points |
By Stories | All values in story counts |
Summary Cards
Four stat cards appear. Their content changes based on the active view (Commitment vs Delivery):
In Commitment View:
Card | Shows |
Increment Commitment | Total planned during increment planning. Subtitle: team count and sprint count. |
Sprint Committed | Total committed at sprint start. Subtitle: drift vs increment plan (green if positive, red if negative). |
Delivered | Total delivered. Subtitle: percentage of sprint committed. |
Commitment Reliability | Reliability percentage based on completed sprints. Color-coded: green >= 80%, amber >= 50%, red < 50%. |
In Delivery View:
Card | Shows |
Sprint Committed | Total committed scope. Subtitle: team and sprint counts. |
Current in Sprint | Current scope in selected sprints. Subtitle: net scope change (amber if positive, green if negative, gray if zero). |
Delivered | Total delivered. Subtitle: percentage of current in sprint. |
Delivery % | Overall delivery percentage. Color-coded. |
Burndown / Burnup Chart
The Burndown / Burnup chart shows how delivery progresses across iterations for selected teams.
You can switch between two chart types:
Burndown Chart
Shows remaining work across iterations.
If the line goes down steadily, delivery is on track.
If the line stays flat or increases, delivery may be behind.
Burnup Chart
Shows delivered work compared to planned work.
Common lines:
Delivery Plan → planned work.
Actual → delivered work.
True Remaining → remaining work.
If delivered stays below plan, teams may be behind.
Team Health Overview
Team Health Overview shows delivery performance for each team in the selected iterations.
In Commitment View
In Delivery View
Values Shown in the Team Health Overview
Field | Description |
Team | The team name for which delivery data is shown. |
Increment Plan | The total amount of work planned for the team in the increment. |
Iteration Commitment | The amount of work the team committed during the selected iterations. |
Current in Iteration | The amount of work currently assigned in the selected iteration. |
Delivered | The amount of work the team actually completed. |
Capacity | The available capacity for the team during the selected iterations. |
Gap / Iteration Gap | The difference between committed work and delivered work. A positive gap means the team delivered less than planned. |
Scope Change | Shows if work was added or removed after the iteration started. |
Average Velocity | The average amount of work the team usually completes per iteration. |
Reliability | Shows how closely the team delivered what they committed. |
Delivery % | Percentage of committed work that was completed. |
Trend | Shows whether the team's delivery is improving, stable, or declining across iterations. |
Single-Team Iteration Details
Only visible when a single team is selected (either by filtering to one team or by clicking a row in the Team Health table).
Iteration Delivery Comparison Chart
The bar chart at the top compares planned, committed, and delivered work for each iteration.
Each iteration shows:
Iteration Committed → work the team committed for the sprint.
Current in Iteration → work currently assigned in the sprint.
Delivered → work completed in the sprint.
Sprint Detail Table
Each row represents one sprint, showing metrics for that sprint. The current sprint row is highlighted in light blue. Future sprints are shown with reduced opacity and a "FUTURE" badge.
Delivery Gaps
Delivery Gaps shows teams that delivered less work than committed.
Large gaps may indicate over-commitment, blockers, scope changes, and capacity issues.
Top Performers
Top Performers show teams meeting or exceeding commitments. Use this section to identify stable teams.
High reliability usually means:
Accurate planning/
Stable velocity.
Controlled scope.
Final Words
In the previous guides, we explored the Analytics workspace and Feature Analytics to understand delivery from a feature perspective.
In this guide, we focused on Team Delivery, which shows how work is committed and delivered by each team across iterations.
Together, these views help you analyse delivery from both the feature level and the team level, giving you a complete picture of execution progress in Kendis.