Tiger Team Velocity 2026

Snapshot of Jira as of October 21, 2026

— tickets completed since January. The busiest month was — with — done. — completed tickets (—%) were SNI work.

Completed, Jan–today—Status 9 - Done
Average per month—Over months with any completions
Median lead time— dCreated to resolved, done tickets
Closed as won't do—Resolved since January
Open now—Not yet done or closed
SNI work completed—of — SNI tickets found

Velocity by month

Tickets completed per month

Bars are tickets resolved that month. The line is new tickets created.

Done Won't do Created

Lead time, created to done

Days from ticket creation to resolution, for tickets finished that month.

Median Average

Month by month

October is month to date.

Month Done Bugs done Won't do Created Median lead (d) Avg lead (d) SNI done

SNI Reports

SNI share of completed work

Done tickets each month, split by whether they were flagged as SNI.

SNI Other

SNI tickets

Flagged when "SNI" appears in the summary, description, labels or comments, when "Schneider" appears, or when the ticket carries a 3–5 digit client ticket number (Ticket ID: 1331, Defect 736, or a summary like 1489 - …).

Ticket Summary Status Resolved Client # Why flagged

How these numbers are worked out

  • This page is a fixed snapshot taken October 21, 2026. It does not update from Jira.
  • Tickets: PSELD tickets labelled TigerTeam (any spelling) that were created or resolved in 2026. This stands in for board 7686's own filter.
  • Velocity is ticket count. None of these tickets have story points, and the board has no sprints, so there are no point-based numbers.
  • Done means status 9 - Done, counted in the month it was resolved. Won't do (status 10) is shown apart and isn't counted as done.
  • Lead time runs from ticket creation to resolution. Older backlog tickets finished this year pull the average up, so the median is the steadier figure.
  • The SNI scan matches the patterns above. It can miss SNI work that mentions neither SNI nor a client ticket number.