Jira Sprint Health Metrics Review Without Gaming
Read burn-down, carry-over and cycle time carefully.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Review sprint metrics. Data for the last six sprints: committed, completed, added, removed, carry-over, bug count, average cycle time and blocked days: [SPRINT_METRICS]. Build a table for the six sprints with committed, completed, completion rate, added, scope change rate and carry-over, plus the averages and the cycle time with its spread; for example sprint 3 committed 24 and completed 18 is 75 percent. Identify patterns and give hypotheses with tests. Explain how each metric can be gamed and what pairing of metrics reduces that: story point inflation paired with the cycle time of equal-sized stories, closing stories early paired with the defect rate after release, and splitting stories paired with value delivered per sprint. Six sprints are a small sample, so state uncertainty. Do not compare teams, since points are relative, and do not use velocity as a performance target. Recommend three retrospective questions, not targets. Return the table and a short narrative; menu paths and field names are unconfirmed until checked [VERIFY].
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.