Spike: Velocity & Volatility

We want to explore the complexity and effort required to implement Team velocity and volatility (&435).

We also want to explore the ideal UI/UX.

MVC 1

• Show the velocity and volatility of an iteration cadence in the iteration cadence list view

MVC 2

• Provide a way to view it in graphical format along the lines of &1956

MVC 3

• If a Board is scoped to the current iteration, show the current velocity and the count of weight on the board

MVC 4

• If a Board has an iteration list, visually show a "cut line" in the list based on the velocity.

Considerations

• Velocity and volatility should be able to be scoped a few different things:
  • Velocity/volatiltiy of iterations within an iteration cadence
  • Velocity/volatility of subgroups/projects where the duration would be weekly (this technically would live outside of iterations and be more of an aggregate metric)
  • Segmentable by attributes like subgroup, project, or label
• We already have https://gitlab.com/gitlab-org/gitlab/-/analytics/issues_analytics, which shows issues opened by month. We'll want to include the velocity data close to the iteration cadences, but the issue analytics page may be a good place for the aggregate level velocity data.

Reading and resources

• https://www.pivotaltracker.com/blog/its-the-volatility-that-will-kill-you
• https://www.pivotaltracker.com/blog/velocity-matters
• http://www.jamesshore.com/v2/books/aoad1/estimating