4 Lenz: Flow Metrics Widgets
Features and Functionality
This article is part of our series on the Features and Functionality of the 4 Lenz Dashboard. We've broken each area down for you, into shorter articles.
There are videos in the Metrics tab article that talk through how manually entered data and how integration data is used to populate the 4 Lenz Dashboard.
Predictability
Sprint Level Predictability displays the percent of committed work items that were completed across the completed sprints for the last 90 days. When integrating with Jira, this widget works for teams pulling in data from Scrum boards (not Kanban boards).
When data has been entered manually for a team, the numbers entered for Committed Points and Completed Points for each sprint that ended in the last 90 days are considered and then averaged to obtain the displayed value.
Variance is shown next to the percentage in the widget in green when there is an increase and in red when there is a decrease. Variance is determined at the individual team level by the following formula: (new value - old value / old value). Variance % is determined for the multi-team level and above by aggregating the percentages for each individual team and dividing by the number of teams to get an average.
Click the three-dot icon to select the Predictability Formula link and see the formula behind the widget when data is populated via an integration.
Throughput
This widget displays both Feature and Story-level Throughput. Change the view using the down arrow in the widget.
Feature Throughput
Feature Throughput displays the number of features that were completed by the team in the last 90 days.
When data is entered manually for a team, the numbers entered for Actual Throughput for each sprint that ended in the last 90 days are considered and then averaged to obtain the displayed value.
Variance is shown next to the percentage in the widget in green when there is an increase and in red when there is a decrease. Variance is determined at the individual team level by the following formula: (new value - old value / old value). Variance % is determined for the multi-team level and above by aggregating the percentages for each individual team and dividing by the number of teams to get an average.
Click the three-dot icon to select the Throughput Formula link and see the formula behind the widget when data is populated via an integration.
Story Throughput
Story Throughput displays the number of stories that were completed by the team in the last 90 days.
When data is entered manually for a team, the numbers entered for Completed Stories for each sprint that ended in the last 90 days are considered and then averaged to obtain the displayed value.
Variance is shown next to the percentage in the widget in green when there is an increase and in red when there is a decrease. Variance is determined at the individual team level by the following formula: (new value - old value / old value). Variance % is determined for the multi-team level and above by aggregating the percentages for each individual team and dividing by the number of teams to get an average.
Click the three-dot icon to select the Throughput Formula link and see the formula behind the widget when data is populated via an integration.
Velocity Delta
Velocity Delta shows by what percent the velocity has improved or declined in the last 90 days. When integrating with Jira, this widget works for teams pulling in data from Scrum boards (not Kanban boards).
When data is entered manually for a team, the numbers entered for Completed Points for each sprint that ended in the last 90 days are averaged and then compared to the average of the numbers entered for Completed Points for each sprint that ended in the last 91-180 days to find the percentage increase or decrease.
Click the three-dot icon to select the Velocity Delta Formula link and see the formula behind the widget when data is populated via an integration.
ROI Efficiency Gained / Avg Story Cycle Time
ROI Efficiency Gained
ROI Efficiency only displays at the multi-team level and above. At the individual team level, this widget displays story cycle time.
ROI Efficiency Gain displays the dollar efficiency gained or lost during the last 90 days. This is determined by the feature throughput variance. ROI Efficiency is improved as the feature throughput increases and declines as the feature throughput decreases.
ROI Efficiency is the same calculation for data from an integration or manually entered data.
Multi-team level calculation: The ROI Efficiency formula at the multi-team level is Total budget x feature throughput variance % / 4 quarters.
We assume a $1,200,000 budget for each team that rolls up to a multi-team. The total budget is determined by multiplying $1,200,000 x the number of sub-teams in a multi-team.
In the example below, the total budget would be $3,600,000 because $1,200,000 x 3 teams = $3,600,000.
The feature throughput variance % for a multi-team is determined by calculating the percentage difference between the total number of features the sub-teams completed in the last 90 days vs the previous 90 days divided by the total number of features completed in the previous 90 days.
In the example below, the feature throughput variance % would be 60% because 8 - 5 / 5 = 6 x 100 = 60%.
|
Features completed in last 90 days |
Features completed in the prior 90 - 180 days |
Variance % |
|
| Multi-team | 8 | 5 | 60% |
| Team 1 | 3 | 2 | |
| Team 2 | 3 | 2 | |
| Team 3 | 2 | 1 |
Using this formula, total budget x feature throughput variance % / 4 quarters, the ROI Efficiency for this multi-team would be $540,000 because $3,600,000 x 60% / 4 quarters = $540,000.
Enterprise level calculation: The ROI Efficiency at the enterprise team level is determined by aggregating the ROI Efficiency from each multi-team that rolls up to the enterprise team.
So if the ROI Efficiency for the two multi-teams that roll up to an enterprise team is $540,000 and $800,000, the ROI Efficiency for the enterprise team is $1,340,000.
Click the three-dot icon to select the ROI Efficiency Gain Formula link and see the formula behind the widget, for the multi-team level.
Average Story Cycle Time
The Avg Story Cycle Time widget is available only at the team level. This widget measures how long it took on average to complete stories over the last 90 days.
When data is entered manually for a team, the number of days entered in the Story Cycle Time field for each sprint that ended in the last 90 days are considered and then averaged to obtain the displayed value.
Variance is shown next to the percentage in the widget in green when there is an increase and in red when there is a decrease. Variance is determined at the individual team level by the following formula: (new value - old value / old value). Variance % is determined for the multi-team level and above by aggregating the percentages for each individual team and dividing by the number of teams to get an average.
Click the three-dot icon to select the Avg Story Cycle Time Formula link and see the formula behind the widget when data is populated via an integration.
Story Points Delivered
This widget displays a timeline of the team's sprints for their selected PI or quarter. The widget displays all the sprints for the selected quarter or Planning Increment and shows target vs actual story points delivered. The quarter is noted next to the widget title. When integrating with Jira, this widget works for teams pulling in data from Scrum boards (not Kanban boards).
When data is entered manually for a team, the numbers entered for Target Points and Actual Points for each sprint are considered and then plotted based on the ‘To’ date of the sprint, which is the end date.
Use the scroll bar to see the data for each Sprint. Change quarters by clicking on the arrows to the left and right of the chart or the dots at the bottom. No data will be displayed for quarters that do not meet the criteria for the widget.
Comments