Cycle Analytics: v1 Rollout
This is the rollout plan for the upcoming Cycle Analytics feature. This will be a great feature and we need to prepare something specific to advocate people on how awesome this feature is.
Definition of the feature
Goal
This feature is part of our vision From idea to production. To help teams ship better code in a faster way, we need to give them tools to measure their velocity. This is where Cycle Analytics shines. It gives an overview on how much time it takes to go from an idea to production for each project you have. Not only do we indicate the total time it takes to achieve this, but we also break this total time down into the multiple stages an idea has to pass through to be shipped.
Audience
- Any team member, decision maker or manager who wants to know the velocity of the team, by showing how quickly the team is going from an idea to production.
Why
- By nature, we need metrics to make better decisions.
- It's easy to think that we are shipping quickly as a team, but perhaps there are a lot of issues which are not being taken care of in a timely fashion and stay stuck at a specific stage. Without metrics and a high level overview, we just don't know. Cycle Analytics is a way to prevent this to happen, and be able to act on how do things better as a team.
Market strategy
In terms of perception, we need to convey the message that we don't only offer tools to manage the code, but also the team behind this code. We have this awesome page for Issue board (https://about.gitlab.com/solutions/issueboard/) - Cycle Analytics falls into the same category of features.
- We definitely need a page like this for this feature (
/solutions/cycle-analytics) - We need a dedicated post around this feature, after the 8.12 post.
Rollout plan
References
- Original issue: #21170 (closed)
cc @amara
Activity
mentioned in issue #21170 (closed)
Added meta label
The marketing plan is listed in this Google Doc and it will have the relevant corresponding issues.
-
Current thoughts on messaging for the landing page:
Section 1
- Hero: Introducing Cycle Analytics
- Sub-head: Real data, better decisions.
Section 2
- Real data
- Estimates of time or level of effort are often incorrect. Stop estimating. Know how many days or minutes it takes your team to get from idea to production.
- Overviews and drill downs
- Measure your team's total and step-by-step velocity. Cycle analytics indicates the total time it takes to move from idea to production as well as the time it takes to move from one stage to another.
- Built for teams and managers
- Use shared metrics to make better decisions. With insights into how long it takes the team to move from idea to production, you can pinpoint areas of improvement and more accurately predict your releases.
-
I asked @regisF this in the landing page issue but it is better asked here:
are there any configurations people have to do for this? If not, then I think the fact that there is no configuration required is stronger benefit than my second bullet point. Also I can just pull the second bullet into the first one.
@amara there will not be any configuration for this feature.
Milestone changed to %8.13