Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your existing Jira Software Cloud site to suit your agile development processes.
Learn how to create, search, and work with issues in software projects, manage your profile, and more.
Learn how to get started, enable features, and manage and administer team-managed projects.
Create powerful rules to start automating your manual, repetitive processes.
Cycle time beacon and the report are helpful insights to teams as they represent the time it takes for your team to ship issues when they flow through the deployment pipeline.
In this article you'll learn:
How to set up the cycle time?
How to understand the cycle time report?
How to reduce your cycle time?
Reading the cycle time report
Understanding the weekly comparison
The weekly comparison chart is a larger version of the Cycle time beacon on the Deployments page, showing the median cycle time of one week compared to the 12 weeks proceeding it. The selected week will display the cycle time for the selected week versus the 12-week median time using a colorful explanation of Cycle time using a color pattern. For instance, Orange lozenge for over and Green one for underperforming cycle time.
Analyzing the trend
The week breakdown depicts all shipped issues within the selected week, using a scatterplot, daily trend line (calculated day by day), and a dotted line showing the week median, which is shown in the weekly comparison chart.
Shipping the issues
This table at the bottom displays the issue data, sequenced with highest cycle time to lowest cycle time. You can sort by the cycle time and review time columns, however, the cycle time column sort is prioritized.
Engineering best practices
Starting small and fast: It is advisable to deliver more by starting with smaller sprints and producing customer deliverables real quick.
Automate, automate, automate: Manual work is a big turn-off for the developers. Using automated tools saves time, energy, and reduces delivery time as well. You can do continuous integration through automated releases and invest the remaining time in coding.
Slicing the giant PRs: Breaking the work-items into smaller chunks and iterating frequently enables the team to perform better. It also reduces the review time for the pull requests significantly.
Assess the impact beforehand: Making sure that what’s the value for the customer and doing market analysis help us foresee the impact way before the product release.
TDD: Test-driven development not only covers the use cases that help build a high-quality product but also aids in creating a future-proof holistic solution.
Innovations: Delivering what is required and what works in the market is amazing. Nevertheless, thinking about what may work with the users and adding that extra touch with some innovation can take us a long way with customer satisfaction.
For more information on the deployments insights, see Enable deployments.
Was this helpful?