L2O Value Stream — Performance Report

Completion Rate

Average of per-sprint completion rates: for each sprint, SP done in that sprint ÷ SP committed to that sprint; then averaged across all sprints. SP committed includes all issues assigned to the sprint, including rollovers from previous sprints. Issues with no Story Points set are counted as 1 SP. Credential rotations with no Story Points are excluded.

Rollover

An issue rolls over when it is not completed (Done) within the sprint it was committed to. Rollover% = 100% − Compl%.

Rework / Rework Event

An issue is counted as reworked when its status moves back to In Development or Discovery & Design from a later stage (QA Testing, UAT Testing, Ready for Deployment, or Done). Rework% = issues with ≥1 rework event ÷ total active issues in the sprint. An active issue is one that had at least one transition into an active status within the sprint window. Each issue is counted once regardless of how many rework events it had. Issues are categorized by rework count: 0, 1, 2, or 3+ rework events (Table 5).

Median

The middle value of a sorted dataset. Unlike the average, the median is not affected by extreme outliers. For example, if 9 issues take 1–5 days and 1 issue takes 90 days, the median reflects the typical experience (e.g. 3d) while the average would be inflated.

Cycle Time

Total lifetime active time: sum of time spent in Discovery & Design, In Development, QA Testing, UAT Testing (while Business Approval = Approval Required only), and Ready for Deployment — across the issue's entire history. On Hold time is excluded. Cancelled issues and credential rotations without Story Points are excluded.

Complete Rules for Reproducing This Report

Data Source & Scope

Project: BIZAPPS
Value Stream: Lead to Opportunity (customfield_23515 = "Lead to Opportunity")
Sprints: S27 (1/20–2/2/2026), S28 (2/3–2/16/2026), S29 (2/17–3/2/2026), S30 (3/3–3/16/2026), S31 (3/17–3/30/2026)
Sprint Board: Lead & Demand Gen Scrum Board (Board ID: 6081)
Sprint IDs: 12637 (S27), 12755 (S28), 12844 (S29), 12876 (S30), [S31 ID TBD]

Exclusions (Applied to ALL Metrics)

1. Cancelled issues: status = "Cancelled" — excluded from board and all metrics
2. On Hold issues: status = "On Hold" — excluded from board and all metrics
3. Credential rotations with null SP: summary contains "Credential Rotation" AND story points is null — excluded entirely
Note: Other credential rotations WITH story points set are included

Story Points Default Rule

Issues with no Story Points: Counted as 1 SP
Field: customfield_10002 (Story Points)
This applies to all SP calculations (committed, done, completion rate)

Deduplication Rule

Each issue counted once in its LAST SPRINT only
- Issues that span multiple sprints (rollovers) are counted only in their final sprint
- Prevents double-counting across sprints
- "Last sprint" determined by the last element in the sprint array (customfield_10100)

Completion Rate Calculation

Per-sprint: SP done in sprint ÷ SP committed in sprint
- SP committed = sum of effective SP for all issues assigned to that sprint (including rollovers from previous sprints)
- SP done = sum of effective SP for issues with status = "Done"
Overall: Average of per-sprint completion rates across all sprints
Formula: (S27_compl% + S28_compl% + S29_compl% + S30_compl% + S31_compl%) ÷ 5

Rollover Calculation

Definition: Issue rolls over when not completed (Done) within the sprint it was committed to
Formula: Rollover% = 100% − Completion%
Note: Measured per-sprint, not per-issue

Rework Rate Calculation

Trigger: Status moves back to "Discovery & Design" or "In Development" from a later stage (QA Testing, UAT Testing, Ready for Deployment, or Done)
Active Issue: One that had at least one transition into an active status within the sprint window
Formula: Rework% = (issues with ≥1 rework event) ÷ (total active issues in sprint)
Important: Each issue counted once regardless of how many rework events it had
Status Order: Discovery & Design (1) → In Development (2) → QA Testing (3) → UAT Testing (4) → Ready for Deployment (5) → Done (6)
Rework = moving from higher number to lower number (specifically to 1 or 2)

Cycle Time Calculation

Scope: Total lifetime active time across entire issue history
Included Statuses:
- Discovery & Design
- In Development
- QA Testing
- UAT Testing (with Business Approval condition — see below)
- Ready for Deployment
Excluded: On Hold time is excluded from all calculations
Method: Parse changelog histories, calculate time between status transitions, sum all active periods
Metric: Use median (not average) to avoid outlier skew
Additional Exclusions: Cancelled issues and credential rotations without Story Points

Median Time in Development

Included: Discovery & Design + In Development time combined
Method: Sum of all time spent in these two statuses across issue lifetime
Exclude: On Hold time
Sample: Issues that had activity in these statuses (n=21 in this report)

Median QA Time

Included: Time in "QA Testing" status only
Sample: Issues that reached QA Testing (n=4 in this report)
Exclude: On Hold time

Median UAT Time (Conditional)

Critical Condition: Only counts time when Business Approval = "Approval Required"
Field: customfield_21131 (Business Approval)
Logic: Track Business Approval field changes alongside status changes. Only accumulate UAT time when:
1. Status = "UAT Testing" AND
2. Business Approval.value = "Approval Required"
Exclude: UAT time when Business Approval is "Approved" or any other value

Work Type Categories

Project: Issues with Project epic OR "Under Attack" in summary/title (12 issues in this report)
BAU: No epic OR BAU epic (14 issues in this report)
Exclusions: Credential rotations and cancelled issues excluded from BAU count
Epic Field: customfield_10014 (Epic Link)

Composition Categories

Easy: 1–2 SP issues
Complex: ≥3 SP issues
Calculation: Percentage of sprint = (Easy SP ÷ Total SP) or count-based for issue metrics

Assignee Metrics

Completion%: Average of per-sprint rates for issues assigned to that person
Rework%: Percentage of assignee's active issues that had rework events
Role Assignment:
- Dev: Primary assignee during development phases
- QA (e.g., QA 1): Assigned only during QA Testing status
QA-specific: MdnQA = median time in QA Testing while that person was the assignee
Note: MdnCycle and MdnDev not applicable to QA-only assignments

Story Points vs Cycle Time (Table 4)

Active time: From first active status → Ready for Deployment or Done (whichever occurs first)
Exclude: On Hold time
Sample: Only issues with cycle time data (excludes issues that never entered active statuses)
Statistics: Median, Average, Min, Max calculated per SP bucket (1, 2, 3, 5 SP)

Rework Distribution (Table 5)

Rework Event: Status moves back to "Discovery & Design" or "In Development" from a later stage (QA Testing, UAT Testing, Ready for Deployment, or Done)
Status Order: Discovery & Design (1) → In Development (2) → QA Testing (3) → UAT Testing (4) → Ready for Deployment (5) → Done (6)
Rework = moving from higher number to lower number (specifically to 1 or 2)
Sample: All S27–S31 issues that meet criteria (project = BIZAPPS, Value Stream = "Lead to Opportunity", not Cancelled, not On Hold, excluding credential rotations with null SP)
Distribution: Issues categorized by rework count: 0, 1, 2, or 3+ rework events

API Endpoints Required

1. Get Issues: POST /rest/api/2/search
- JQL: project = BIZAPPS AND "Value Stream" = "Lead to Opportunity" AND sprint in (12637, 12755, 12844, 12876, [S31])
- Fields: summary, status, assignee, customfield_10002, customfield_10100, customfield_23515, customfield_21131, created, resolutiondate, customfield_10014
- Expand: changelog
2. Get Sprints: GET /rest/agile/1.0/board/6081/sprint
- Retrieve sprint dates and boundaries
3. Parse Sprint String:
- Format: "com.atlassian.greenhopper.service.sprint.Sprint@...[id=XXXX,name=S##: L2O ...]"
- Extract id, name, state from string using regex

Changelog Processing

Sort: Order histories by created date (ascending)
Track: For each history item where field = "status":
- fromString (previous status)
- toString (new status)
- created (timestamp)
Track Business Approval: For each history item where field = "Business Approval":
- toString (new value)
- created (timestamp)
Calculate Durations: Time between transitions = current timestamp − previous timestamp