Sprint Pack help

Anomalies

Sprint Pack flags a sprint when its data is wrong or unusual in a way that would distort averages: dates in the wrong order, a start date moved by days, a sprint closed within an hour, a sprint started empty, a reopen, or an estimation field changed during the sprint.

Flags are about bad data, not performance. A sprint with a 450% scope change, a low say/do or many carry-overs is not flagged. See why flagged sprints are left out.

Where flags show:

Flags are worked out each time a view or rollup is built, so fixing the data in Jira clears the flag.

Dates reversed

Code: dates-reversed.

The sprint’s start date is after its close date, or, for a sprint that hasn’t closed, after its planned end.

Start date moved

Code: start-moved.

The sprint’s start date differs by more than 24 hours from the moment it was actually started.

Closed within an hour

Code: very-short.

The sprint closed less than an hour after it started.

Usually a test sprint, or a sprint started and closed by mistake.

Started empty

Code: nothing-committed.

A closed sprint had nothing committed at its start.

Reopened

Code: reopened.

The sprint was closed and then reopened.

Estimation field changed

Code: estimation-changed-mid-sprint.

The board’s estimation field changed between the sprint’s start and its close.

Why flagged sprints are left out of averages

Flagged sprints stay in every table and export, with their flag, but they’re left out of averages, medians, trend arrows and the “last say/do”.

Why: one bad sprint can dominate an average. A sprint with its start after its close once produced “Last say/do 0% ↓” as a portfolio headline: a number about a data mistake that read like a verdict on the team. Leaving it out of summaries keeps the headline about the team’s work; keeping it in the table keeps it visible and fixable.

Not flagged either: