Next iterations of DevOps adoption table - discussion issue
Overview
Now that we are close to an MVC for DevOps Adoption at both the instance and group level, let's use this issue to discuss what this feature should look like 6 months from now.
JTBD
Aspirational job)
Driving value through DevOps transformation (As an engineering director, when I have multiple teams in my organisation adopting new DevOps practices, I want to measure the impact on our development and CI/CD activities, so that I can understand ROI and report to leadership on the value of our DevOps transformation.
Big job)
Tool evaluation (- Justifying renewal (User story): As a business leader, I need to demonstrate that GitLab is being adopted by teams so I can justify renewing our contract.
- Justifying upgrade (User story): As a business leader, I need to evaluate how mature our adoption of GitLab is so I can determine whether we are ready to upgrade to the next tier.
Big job)
Opportunities for improvement (- Experimenting on performance (User story): As an engineering leader, I want to experiment with new DevOps processes/tools in my workflows, so that I can improve productivity and time to value.
- Spotting high performers (User story): As an engineering leader, I want to identify which teams have been most successful in their adoption of GitLab so we can learn from their successes.
- Spotting low performers (User story): As an engineering leader, I want to see which teams haven't adopted GitLab so I can identify training opportunities.
- Healthy competition (User story): As an engineering leader, I want teams to understand how their DevOps adoption compares to other teams to create some competition and speed up adoption.
Edited by Larissa Lane