Group Cycle Analytics Over Time
Updated Description
Problem to solve
PMs / Scrum Masters usually work across multiple teams and currently they cannot see cycle time or cross team dependencies on a group level. This makes it very difficult for them to manage the delivery of multiple teams and understand where the bottlenecks are. Engineering Executives would like to understand how fast their organization is moving and compare between projects / groups in order to identify patterns leading to loss of efficiency.
Intended users
Scrum Master, Product Manager, Executive
Proposal
A scrum master would like to be able to consolidate multiple groups or projects in one dashboard, but having a view of all projects in a group is a good start.
-
Given we will only have group level analytics so far, a user should be able to filter by project, subgroup, author, assignee, milestone or specific calendar dates using a date picker (http://www.daterangepicker.com).
-
Let's have a scatterplot with the specific day of completion on the x-axis and number of days it took from
X
toY
as our first attempt to answer the question as to whether people are getting better with time. The chart should contain a trend line (rolling median - 30 days?)+ 25-75% quantile bands. We should have a dropdown where a user can select which stage they want to look at and they should be able to select more than one, so that the trend line will be the sum of days for those stages selected. We can have different color dots representing the different stages. If this looks too messy, we can combine the stages in 1 dot. -
Let's have an area chart, similar to a cumulative flow graph, where we chart the rolling median for each stage over time. The idea would be that when we can customize the stages, we can potentially represent as cumulative flow digram.
If a person selects a period less than 30 days, we show no data in the charts? @cperessini, what would be a better UX? This is something we should think about as if people use scrum they would most likely filter by milestone but if they use kanban, they are most likely to use the date picker.
I would suggest for the 2 charts to go in 1 line under the table we have right now.
Permissions and Security
The dashboard should inherit the project/ groups permissions of users, i.e. I can only see an aggregation of subgroups, projects I have access to.
Documentation
Testing
What does success look like, and how can we measure that?
Measure: We should include the page in user ping to start with and measure how many people visit and how long they stay on it.
Success: As we develop this further, we expect users to spend a significant time deep diving on the page at least once a week.
Links
https://docs.gitlab.com/ee/user/project/cycle_analytics.html