LOPS Scope Creep Report

Generated: 2026-03-02 11:39 EST | Data Source: JIRA | Tickets Analyzed: 1131

Sprint Range:
Showing 10 of 31 sprints

Definitions

Committed

Tickets in the sprint at or before sprint start. This is the original plan.

Added Mid-Sprint

Tickets moved into the sprint after it started. This is scope creep.

Removed Mid-Sprint

Tickets moved out of the sprint after it started. May indicate re-prioritization.

Completed

Tickets in Done/Closed/Verified status at sprint end.

How to Read This Report

Charts

Summary: Scope change and commitment rate trends with rolling averages to show trajectory.

Scope by Tickets/Points: Per-sprint breakdown of committed vs added vs removed work.

Completion: What happened to work at sprint end — completed vs rolled over.

Detail Tabs

Sprint Detail: Drill down to see exactly which tickets were added/removed per sprint and by whom.

Type Breakdown: Are additions bugs (reactive) or stories (planning issues)?

Attribution: Who is moving tickets into/out of sprints most frequently?

Data Source

project = LOPS AND "products[select list (multiple choices)]" IN (tfMRD, "Latitude (tfMRD)") AND "team[team]" = fee007ac-475e-494f-b3b7-91697cf32c09

Sprint Calendar

All sprints in reverse chronological order (most recent first) with their start and end dates from JIRA. Use this as a reference when analyzing sprint data.

Excluded Sprints

The following sprints are filtered from all metrics in this report:

  • 9 sprints before Sprint 34 (legacy data)
  • 2 sprints matching prefixes ["LOPS WH"]: LOPS WH 20250407 (40), LOPS WH 20250602 (44)
Sprint Full Name Start Date End Date Status
Sprint 63 LOPS-tfMRD-63-20260223 2026-02-23 2026-03-09 active
Sprint 62 LOPS-tfMRD-62-20260209 2026-02-09 2026-02-23 closed
Sprint 61 LOPS-tfMRD-61-20260126 2026-01-26 2026-02-09 closed
Sprint 60 LOPS-tfMRD-60-20260112 2026-01-12 2026-01-26 closed
Sprint 59 LOPS-tfMRD-59-20251229 2025-12-29 2026-01-12 closed
Sprint 58 LOPS-tfMRD-58-20251215 2025-12-15 2025-12-29 closed
Sprint 57 LOPS-tfMRD-57-20251202 2025-12-01 2025-12-15 closed
Sprint 56 LOPS-tfMRD-56-20251117 2025-11-17 2025-12-02 closed
Sprint 55 LOPS-tfMRD-55-20251103 2025-11-03 2025-11-17 closed
Sprint 54 LOPS-tfMRD-54-20251020 2025-10-21 2025-11-03 closed
Sprint 53 LOPS-tfMRD-53-20251006 2025-10-06 2025-10-20 closed
Sprint 52 LOPS-tfMRD-52-20250922 2025-09-22 2025-10-06 closed
Sprint 51 LOPS-tfMRD-51-20250908 2025-09-08 2025-09-22 closed
Sprint 50 LOPS-tfMRD-50-20250825 2025-08-26 2025-09-06 closed
Sprint 49 LOPS-tfMRD-49-20250811 2025-08-12 2025-08-25 closed
Sprint 48 LOPS-tfMRD-48-20250728 2025-07-29 2025-08-11 closed
Sprint 47 LOPS-tfMRD-47-20250713 2025-07-15 2025-07-28 closed
Sprint 46 LOPS-tfMRD-46-20250630 2025-07-01 2025-07-14 closed
Sprint 46 LOPS Sprint 20250630 (46) 2025-06-30 2025-07-14 closed
Sprint 45 LOPS Sprint 20250616 (45) 2025-06-16 2025-06-30 closed
Sprint 44 LOPS Sprint 20250602 (44) 2025-06-02 2025-06-16 closed
Sprint 43 LOPS Sprint 20250519 (43) 2025-05-19 2025-06-02 closed
Sprint 42 LOPS Sprint 20250505 (42) 2025-05-05 2025-05-19 closed
Sprint 41 LOPS Sprint 20250421 (41) 2025-04-08 2025-05-05 closed
Sprint 40 LOPS Sprint 20250407 (40) 2025-04-07 2025-04-19 closed
Sprint 39 LOPS Sprint 20250324 (39) 2025-03-24 2025-04-07 closed
Sprint 38 LOPS Sprint 20250310 (38) 2025-03-10 2025-03-24 closed
Sprint 37 LOPS Sprint 20250224 (37) 2025-02-24 2025-03-07 closed
Sprint 36 LOPS Sprint 20250210 (36) 2025-02-10 2025-02-21 closed
Sprint 35 LOPS Sprint 20250127 (35) 2025-01-27 2025-02-07 closed
Sprint 34 LOPS Sprint 20250113 (34) 2025-01-13 2025-01-25 closed

Total: 31 sprints shown

Scope Change Rate Trend

Net scope change (additions - removals) as a percentage of committed tickets. Lower is better. The rolling average smooths sprint-to-sprint variation.

Commitment Rate Trend

Percentage of committed tickets that were completed. Higher is better. Shows how well the team delivers on its sprint plan.

Sprint Scope Analysis (Tickets)

Shows how sprint scope changes after planning. Committed = tickets planned at sprint start. Added = tickets added mid-sprint (scope creep). Removed = tickets pulled out mid-sprint. The Scope Creep % line shows net additions as a percentage of the original commitment.

Sprint Scope Analysis (Story Points)

Same analysis by story points to see effort impact. Toggle between Dev, QA, and Combined points to identify where scope creep comes from.

Completion & Rollover

Shows what happened to work at sprint end. Completed = tickets marked Done/Closed/Verified. Not Completed (Rollover) = tickets still in sprint but not Done — these typically roll to next sprint. The Rollover Rate % line shows the percentage of sprint work that didn't finish.

Note: This tracks tickets that remain in the sprint when it ends. Tickets proactively moved out before close appear in the "Scope (Tickets)" tab as "Removed Mid-Sprint".

Sprint Detail

Click on a sprint to expand/collapse the ticket details. Shows which tickets were added or removed mid-sprint and who made the change.

LOPS-tfMRD-63-20260223 +7 added · -1 removed
LOPS-tfMRD-62-20260209 +3 added · -10 removed
LOPS-tfMRD-61-20260126 +10 added · -8 removed
LOPS-tfMRD-60-20260112 +6 added · -5 removed
LOPS-tfMRD-59-20251229 +5 added · -18 removed
LOPS-tfMRD-58-20251215 +4 added · -1 removed
LOPS-tfMRD-57-20251202 +4 added · -18 removed
LOPS-tfMRD-56-20251117 +1 added · -13 removed
LOPS-tfMRD-55-20251103 +3 added · -15 removed
LOPS-tfMRD-54-20251020 +2 added · -7 removed
LOPS-tfMRD-53-20251006 +6 added
LOPS-tfMRD-52-20250922 +8 added · -25 removed
LOPS-tfMRD-51-20250908 +18 added · -20 removed
LOPS-tfMRD-50-20250825 +8 added · -18 removed
LOPS-tfMRD-49-20250811 +16 added · -10 removed
LOPS-tfMRD-48-20250728 +10 added · -1 removed
LOPS-tfMRD-47-20250713 +31 added · -6 removed
LOPS-tfMRD-46-20250630 +37 added · -5 removed
LOPS Sprint 20250630 (46) +6 added · -10 removed
LOPS Sprint 20250616 (45) +40 added · -23 removed
LOPS Sprint 20250602 (44) +71 added · -6 removed
LOPS Sprint 20250519 (43) +5 added
LOPS Sprint 20250505 (42) +8 added
LOPS Sprint 20250421 (41) +24 added · -1 removed
LOPS Sprint 20250407 (40) +58 added · -9 removed
LOPS Sprint 20250324 (39) +12 added · -3 removed
LOPS Sprint 20250310 (38) +15 added
LOPS Sprint 20250224 (37) +11 added · -3 removed
LOPS Sprint 20250210 (36) +4 added · -1 removed
LOPS Sprint 20250127 (35) +7 added · -2 removed
LOPS Sprint 20250113 (34) +13 added

Additions by Issue Type

What types of work are being added mid-sprint? Bugs/Defects suggest reactive scope changes (issues found during sprint). Stories/Tasks suggest planning gaps or changing priorities.

Scope Change Attribution

Who moved tickets into and out of sprints across the analyzed period. Aggregated across all sprints shown in the report.

Context: This shows who moved tickets in Jira, not necessarily who requested the change. External factors (lab scope changes, production issues) may require team members to adjust sprint scope. Use this data to understand patterns, not assign blame.

Person Tickets Added Tickets Removed Net Change
hyakan@natera.com 62 128 -66
masmith@natera.com 130 35 +95
hshapiro@natera.com 68 3 +65
vaponte@natera.com 52 17 +35
ttapscott@natera.com 10 30 -20
joquinn@natera.com 36 2 +34
ivargas@natera.com 20 2 +18
kfusha@natera.com 13 0 +13
renson@natera.com 12 0 +12
dhughes@natera.com 1 11 -10
vkumaev@natera.com 10 1 +9
keddy@natera.com 11 0 +11
ykhmelnik@natera.com 3 4 -1
ykalinicheva@natera.com 4 2 +2
oandrusenko@natera.com 5 0 +5
pmarkovic@natera.com 3 2 +1
lskorokhod@natera.com 2 2 0
amnguyen@natera.com 2 0 +2
sojha@natera.com 2 0 +2
epobirskiy@natera.com 2 0 +2
jcolca@natera.com 2 0 +2
iimai@natera.com 1 0 +1
nkolesnikov@natera.com 1 0 +1
apakhunov@natera.com 1 0 +1