DCX Cycle Time - Trend Analysis

Agile Change Management Workflow - SDLC

DCX Target Lead Time per JIRA Ticket State • Target: 57 days • Issue types: Story, Task, Bug, Defect, Technical Debt, Security

🔍

Pending Analysis

Newly created PBIs that need to be enriched by Product Owner

13 days

▶

✎

In Analysis

Team refines PBI towards meeting DoR

9 days

▶

⚙

To Do (Ready)

Select future sprint candidates. PO confirms priority

11 days

▶

💻

In Development

Team builds PBI to meet Acceptance Criteria

4 days

▶

🔎

Code Review

Team peer reviews and checks code quality best practices

1 day

▶

✅

Testing

Team evaluates Acceptance Criteria and ensures DoD was accomplished

3 days

▶

📋

Done (Waiting for PO Approval)

PO reviews testing evidences and acceptance criteria, approves PBI

4 days

▶

🚀

Approved (Waiting to Deploy)

PBI is approved and waiting to be shipped to PROD

12 days

= 57 days

Portfolio Cycle Time

Overall DCX portfolio cycle time trend across all projects and teams (from "DCX CycleTime per Month" sheet)

▶ Reference Data

Portfolio Status Heatmap

Monthly average cycle time per status across all teams. Color-coded: Green = at or below target, Red = far above target.

Status Cycle Time - Heatmap

Color-coded table: Green = at or below target, Red = far above target. Values in days.

Team Trend Analysis

Elapsed cycle time trend per team over time. Filter by Product Group and Team to track progress toward the 50-day target.

▶ Data Table

Pull Requests Merged

Track the number of pull requests merged per team over time. Filter by Product Group and Team to analyze PR throughput.

Source: all "Team Data" sheets in the uploaded workbook (e.g. June & Aug), combined. Each product is one line connecting its "Without AI" baseline and each sheet's "With AI" measurement. Use the Metric toggle to switch between PRs per contributor and total PRs merged. Hover a point for its phase and source sheet.