Capacity Planning for GitLab Instances - Generic
Context
We have developed a tool and process to manage our capacity planning process at GitLab. This process is required for SOX controls on mission critical software.
We display our saturation predictions with a web ui and manage our alerts and process in our capacity planning trackers.
Hypothesis
Preamble
Enterprise GitLab customers are required to implement capacity planning processes for key software components that they run as part of their business. GitLab is mission critical software for these customers.
Statement
If we introduce capacity planning for the GitLab application into the product, we will reduce toil for GitLab admins and create product differentiation resulting in greater customer satisfaction and improved availability of GitLab for self-managed customers. Some customers are required to have capacity planning in place for mission critical software via SOX compliance or similar.
Research questions
- What percentage of customers have a capacity planning process for GitLab?
- What percentage of customers have a requirement for their GitLab instance to be included in capacity planning?
- How much work/time do those customers spend on capacity planning?
- How many (if any) capacity planning/saturation related incidents have those customers experienced?
- Are customers interested in GitLab "self capacity planning"?
Problem validation
Issue links go here
Solution Validation
Issue links go here