The delivery by teams section in Analytics focuses on providing the progress by teams from multiple different dimensions including
Progress by Feature
Team Progress by Stories and Story Points (Estimate)
Feature Progress (by story)
Cumulative data of Teams Planning
Individual team progress
1. Progress by Feature
This widget shows the completion of the features worked by each team. The percentage is calculated based on the status of the feature. If a feature is worked on by multiple teams, it will be counted in each of the team's progress.
The color of the bars represents each team and their progress is marked by the completion of their feature.
2. Progress by Team Stories
This widget shows the progress of teams based on the stories assigned to a team. Assignment to a team means the stories are in one of the team sprints at Kendis board.
There are 2 options to view the progress
By Estimate: Based on the story points of the stories that are done.
Progress = (Sum of story points of the team stories that are done) / (Sum of story points of all the stories assigned to a team) * 100.
By Estimate: Based on the number of stories that are done.
Progress = (Count of team stories that are Done) / (Count of all the stories assigned to a team) * 100.
3. Progress by Feature/Planned
This is perhaps a bit thicker to understand but once it's clear how this widget works, you can get a better understanding of the feature completion by your teams.
In the first 2 widgets, Progress by Features and Progress by Team stories, the percentage is based on either the feature status or story status.
However, in case a feature is being worked on by multiple teams, it's often challenging to understand whether a team is DONE with their part of the feature delivery or not. With this widget, we will provide you with this specific number.
Let's take an example of Team CRM, in the widget above, the percentage is shown as 18% completed.
Team CRM is working on 11 features and for 2 features they have completed ALL of the stories that were assigned to them, although the feature itself is still open and not completed.
For example, FEA-5 is still in progress, however, both of the stories assigned to Team CRM are in DONE category, so for the calculation purposes, Kendis will consider this feature FEA-5 as DONE and will count towards the 18% completion that is shown for this team.
Again the percentage is shown based on the count and estimate (story points)
Progress by Count: (Number of features where the stories are done)/(Total number of features that are worked by the team) * 100
Progress by Estimate: (Sum of story points of the stories that belong to a feature where all the stories are completed by the team)/ (Sum of story points of all the stories worked by the team) * 100
4. Cumulative data of Teams Planning
This table shows the important information about each team's planning.
Number of Features and their breakdown (To Do, In Progress, Done)
Number of Stories and their breakdown (To Do, In Progress, Done)
Number of Story Points (Estimate) and their breakdown (To Do, In Progress, Done)
Capacity: Sum of capacities of all the sprints for each team.
Load: Sum of story points for each team
Capacity - Load: Show whether teams have over or under planned. Red circle means teams have OVER PLANNED (have more stories than their capacities).
Planned Sum: Features that are planned in the team sprints. If a feature has a story in one of the team sprints, then it will be considered as a "Planned Feature".
Unplanned Sum: Features that are not in any of the team sprints, so in simple words, no one is working on them.
Note: At the board area, there is a filter for planned/unplanned features and stories.
Important: In this table, you can't click on the numbers to view the details. This may change in the future. All other areas and numbers in analytics is clickable to show the relevant information.
5. Individual Team Progress
In this section, users can get a quick overview of individual team progress. It shows 4 bars for each sprint
Capacity: The capacity of this team for this sprint
Load: Sum of story points for all the stories in this sprint
Done Story Points: Sum of all the story points done in this sprint.
Committed Load: Sum of the story points when the sprint started (it's kind of baseline to remember what team committed at the start of sprint)