Cycle Time for Changes KPI

Why Cycle Time for Changes Matters

• Increase Efficiency: Shorter cycle times mean faster delivery of features and fixes.

• Identify Bottlenecks: Spot stages where work stalls (e.g., QA, UAT) and target improvements.

• Boost Predictability: Consistent, low cycle times build stakeholder confidence.

How to Calculate Cycle Time for Changes

Cycle Time = Issue Completion Time – Issue Creation Time

(Opsera averages this across all resolved issues in your selected period.)

Example:

5 tickets resolved with cycle times of 2h, 3h, 1.5h, 4h, and 2.5h → Average Cycle Time = (2+3+1.5+4+2.5) / 5 = 2.6 hours

How Opsera Helps You Track Cycle Time

1. Trend Chart

   • Bar chart showing average cycle time per interval; click any bar to drill into that batch of issues.

2. Compare Chart

   • Side-by-side bars per Jira status (e.g., Done, QA, UAT) comparing your personal vs. project average performance.

   • Color-coded: Yellow = your data; Purple = project average.

3. Top Projects Highlight

   • Automatically flags the projects with the longest cycle times in orange, so you know where to focus first.

4. Comprehensive Issue Table

   • Lists each issue with: key, status, created/completed timestamps, first-commit & coding durations, total cycle time, assignees, project, issue type, and commit links.

Best Practices to Reduce Cycle Time

• Break Work into Smaller Tasks: Deliver in bite-sized increments to expedite flow.

• Automate Testing & Reviews: Shift quality checks left so fewer issues bubble up late.

• Use Dashboards & Alerts: Monitor real-time cycle times to catch spikes early.

• Document and Refine Workflows: Standardize steps for each status (e.g., “Submit to QA”) and optimize over time.

• Leverage Compare Chart: Identify outliers and coach underperforming stages or team members.

FAQ

1. What must I configure before viewing this KPI? Create a Group Mapping with filters for Defect Type, Exclude Issue Status, Include Issue Status, Issue Completion Status, Issue Types, Jira Board, JQL Filters and Project Name.

2. Can I customize which Jira statuses count toward cycle time? No—Opsera uses all “created” → “completed” transitions. Use Exclude Status in your mapping to omit unwanted workflows.

3. How do I interpret the Compare Chart bars? The X-axis shows Jira statuses; the Y-axis is time. Yellow bars are your selected assignee’s data; purple bars are the overall project average.

4. Why am I seeing unusually high maximum cycle times? That reflects the single longest issue duration—use the table to identify that issue and diagnose delays (e.g., blocked in UAT).

5. How frequently does this KPI update? In real time—as soon as issues move to “Completed” in Jira and your group mappings are applied, the charts and tables refresh.

6. Can I use JQL queries to filter which issues are included in cycle time?

   Yes—you can now select saved Jira filters directly in the Opsera dashboard to apply JQL-based filtering. This is useful when you need more granular control than project/status/issue type alone provides. In the tool mapping, choose from your saved Jira filters under the "JQL Filters" option. The dashboard will calculate cycle time only for issues returned by that query.