Sleuth tracks change lead time, defined as the time from your first commit to deploy, for all your code deployments and for each configured environment. Because Sleuth tracks deployments and not just pull requests or branches we can provide an accurate change lead time that includes all the commits and pull requests that went into a deploy.
For instance, let's say that you deploy every merged pull request to your staging environment. However, let's also say that you bulk up all changes made in a day in staging and deploy them together to your production environment. With this style of work you'll see small change lead times for each staging deploy. However, the change lead time for your production deploy will include all the pull requests and the extended deploy time it took for them to make it to production.
The Sleuth project metrics dashboard shows the average lead time for all deploys in the period. We also provide a detailed breakdown of how much your team, on average, is spending:
Coding - the time spend from first commit to when a pull request is opened
Review lag time - the time spend between a pull request being opened and the first review
Review time - the time spent from first review to the pull request being merged
Deploying - the time spent from pull request merge to deployment
In addition to the averages found on the metrics dashboard you can always see exactly where time was spent for each deploy via its detailed view.
For a more detailed timeline, including events from issue creation to deploy verification, you can always consult the timeline for each deploy.
Sleuth supports feature flags as a first class form of change. That said, feature flags are an instantaneous change to your running deployments. Therefore feature flags don't have a lead time or breakdown. Sleuth excludes feature flag changes from the lead time graph and associated deploy list.
Sleuth uses our code integrations (Github, Bitbucket, Gitlab, etc) coupled with our deployment tracking to build a complete picture of your team's lead time, the time from first commit to deploy. Once you've connected your code to Sleuth and setup your first Code Deployment Sleuth automatically tracks your change lead time for each deploy.