-
Suggestion
-
Resolution: Unresolved
-
1
-
4
-
Problem description
This evening I tried several ways to get cycle time metrics in a next-gen kanban project. However, none were really successful:
- the reports section pretty much lacks any kanban metric reports. It only has two scrum metric reports (velocity and burndown charts
- In the dashboard I tried several chart gadgets:
- Average time in status:
- hard to read due to it being displayed as a line chart, it would be easier to read as a grouped bar chart with groups per day/month/year, where the bars within the group indicate a state, and the y-axis contains the average.
- I found the status multiselect somewhat unusable. For the statuses displayed came from all projects, even though the filter I entered earlier only selected stories from a single project. In turn, this lead to multiple done statuses being displayed in the multi-select. It would be easier if the statuses would be derived from the issues captured by the project selected or issues returned from the filter.
- Two dimensional filter statistics
- Does a better job with regard to status, than 'average time in status.'
- Unfortunately lacks an average time spent in board status.
- Average time in status:
Possible solutions
- add the control chart for next-gen projects
- enhance some of the gadgets above to visualise clearly how long, on average, issues spent in a certain column on the kanban board.
- add a new cycle time gadget for dashboards
Way to measure cycle-time / average time in board column in team-managed projects
-
Suggestion
-
Resolution: Unresolved
-
1
-
4
-
Problem description
This evening I tried several ways to get cycle time metrics in a next-gen kanban project. However, none were really successful:
- the reports section pretty much lacks any kanban metric reports. It only has two scrum metric reports (velocity and burndown charts
- In the dashboard I tried several chart gadgets:
- Average time in status:
- hard to read due to it being displayed as a line chart, it would be easier to read as a grouped bar chart with groups per day/month/year, where the bars within the group indicate a state, and the y-axis contains the average.
- I found the status multiselect somewhat unusable. For the statuses displayed came from all projects, even though the filter I entered earlier only selected stories from a single project. In turn, this lead to multiple done statuses being displayed in the multi-select. It would be easier if the statuses would be derived from the issues captured by the project selected or issues returned from the filter.
- Two dimensional filter statistics
- Does a better job with regard to status, than 'average time in status.'
- Unfortunately lacks an average time spent in board status.
- Average time in status:
Possible solutions
- add the control chart for next-gen projects
- enhance some of the gadgets above to visualise clearly how long, on average, issues spent in a certain column on the kanban board.
- add a new cycle time gadget for dashboards