Productivity Analytics - Type of Work

Problem to solve

While we started tackling productivity analytics in https://gitlab.com/gitlab-org/gitlab-ee/issues/12079, there is a lot more information that can be conveyed to EMs in order to optimize their groups. Some of the questions we would like to help answer are:

• What are engineers working on:

• We should classify code as New, Churn (Number of LOCs changed that have existed for less than 1 month), Refactoring (Number of LOCs changed that have existed for more than 1 month. At the top of the productivity analytics page, this can be the first chart we present before we deep down into MRs?

Permissions and Security

The dashboard should inherit the project/ groups permissions of users.

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 / references