Few teams can answer how long their software projects take and fewer can answer how long each stage in the process takes. Without this information, you do your best to estimate the time or level of effort that it will take to get from an idea to customer-ready code.
Unfortunately, most teams are flying blind on their estimates using past experiences and best guesses to offer a semblance of how long it’ll take to complete a project. It’s no wonder why estimates are often incorrect.
We built Cycle Analytics to stop blind estimation and instead show you real data on your team’s velocity. You'll see how long the total process takes as well as how much time you spend in each stage.
Last week, we wrote a "feature preview" on what Cycle Analytics is and how it can help your team. The TL;DR takeaway from that post was: reducing cycle time is a competitive advantage. Cycle Analytics helps you uncover how long it actually takes to complete your development process. A shared view of the team's velocity is the first stage to improving it.
Cycle Analytics tracks the median time it takes your team to complete every stage in the modern development process.
Cycle Analytics Stages
- Issue (Tracker) - Median time from creating an issue to assigning the issue to a milestone or adding the issue to a list on your Issue Board
- Plan (Board) - Median time from giving an issue a milestone or adding it to an Issue Board list to the pushing first commit
- Code (IDE) - Median time from the first commit to creating the merge request
- Test (CI) - Median of the time CI takes to run every build for the related merge request
- Review (Merge Request) - Median time from creating the merge request to merging it
- Staging (Continuous Deployment) - Median time from MR merge until deploy to production
- Production (Total) - The time it takes between creating an issue and deploying the code to production
Note: This the first iteration of Cycle Analytics. As you know, we ship the smallest thing to provide initial value and then we learn from your feedback and continue to improve the feature over time. We have ideas about what we will build next for Cycle Analytics but we'd love to hear your thoughts. You can follow and contribute to the discussion on this issue.
In recent months, we've talked a lot about our vision of being an integrated set of tools for the full software development lifecycle. Cycle Analytics is another testament to the benefits of having an integrated toolset. The reason we are able to measure cycle time is because GitLab stores all of the data around your development efforts, and the associated metrics, in one central data store. Now, we're able to surface that data through Cycle Analytics. However, it's important to note that Cycle Analytics tracks cycle time based on the GitLab Flow. Therefore, there are some noteworthy dependencies.
Cycle Analytics & GitLab Flow
environmentis set to
production. For Cycle Analytics to track your cycle time, you'll need to configure GitLab CI.
Closes #xxx, where
xxxis the issue number related to this commit.
Closes #xxxto the description of the MR.
We recognize that every team does not follow the same flow. And while GitLab is a flexible product, we are also building an opinionated product that’s aimed at helping you move faster from idea to production. Our CEO, Sid Sijbrandij, shared his thoughts on GitLab Workflow best practices. We hope that they help simplify your workflow within GitLab.
On September 22nd, Cycle Analytics will be available in GitLab.com, GitLab Community Edition, and GitLab Enterprise Edition. Getting started is the same in all three products. All you have to do is navigate to your Project’s Pipelines tab and then select Cycle Analytics to see your project's dashboard.
Keep in mind that if you're working in a new project and you haven't deployed anything to production then you won't see any data on your Cycle Analytics dashboard.