Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Category Direction - Planning Analytics

Category Planning Analytics
Stage Plan
Group Project Management
Maturity Minimal
Content Last Reviewed 2021-08-03

Introduction and how you can help

Thanks for visiting the direction page for Planning Analytics in GitLab. This page is being actively maintained by the Product Manager for the Project Management group. If you'd like to contribute or provide feedback on our category direction, you can:

  1. Comment and ask questions regarding this category vision by commenting in the public epic for this category.
  2. Find issues in this category accepting merge requests.


The DevOps lifecycle begins with planning. An idea is generated by a contributor - be it a support specialist, product manager, or community member - and is scheduled for development alongside many other feature improvements and bug fixes. In context with value stream management, it's the top of our funnel for new initiatives to be developed and eventually see their way to production. As organizations scale and resource management becomes more valuable - and more challenging, with hundreds or thousands of contributors - a strong need quickly emerges to optimize project management and find bottlenecks.

Planning Analytics seeks to deep-dive into the Plan stage of the DevOps lifecycle, by providing insight into your instance's planning activity.

Where we are Headed

The Project Management group is focused on consolidating Issues, Requirements and Epics into Work Items. Rationalizing the backend implementation will allow us to build Planning Analytics more efficiently in the future.

Target Audience and Experience

Development Team Leads and Product Managers.

What's Next & Why

Scrum, ScrumBan, and ExtremeProgramming currently hold 82% of the "agile methodology market share". To better support teams leveraging one of these methodologies, we're going to add support for calculating Iteration velocity and volatility. We will surface velocity data in areas of the product where teams estimate issues and plan Iterations so that they can set more realistic expectations on what they will be able to complete in upcoming Iterations based on the standard deviation of their historical rate of delivery.

Maturity Plan

This category is currently Minimal. The next step in our maturity plan is achieving a Viable state of maturity.

Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license