Product
Everything Sprintwise does, and how
A readiness check before planning, scope tracking during the sprint, and a one-page report after it.
Readiness check
Paste a story or import a CSV, and each story gets a score out of 100 from nine fixed rules. No AI sets the score: in a project, the same story always gets the same number, and every lost point comes with a reason.
It also flags signs of an AI draft pasted without a careful read, such as chat leftovers (“Certainly! Here's…”), unfilled placeholders and criteria that would fit any story, as worth a second look. Leftovers and placeholders keep a story from being Ready.
The backlog keeps your priority order, which you set by dragging. You can also list it weakest first, search it, filter it by band, status, epic or type, and change several stories at once.
Ready
80 or more
Needs work
50 to 79
Not ready
Below 50
The nine rules
Each project can change the maximum story size and the vague-word list. Saving the settings re-scores every story. When one missing thing fails two rules, such as no criteria (so nothing to test), it shows as one reason with both rules' points.
| Rule | Check | How it's checked | Points |
|---|---|---|---|
| C1 | Has enough acceptance criteria | One criterion per line, and more for bigger stories: 1 up to 3 points, 2 from 5 points, 3 from 13. Leading dashes, bullets and numbers are ignored. Criteria under an “Acceptance criteria” heading in the description count too, for Jira projects without a separate field. | 20 |
| C2 | Follows story format for a named user | The title or description reads “As a … I want … so that …”, in that order, and names who it's for. “As a user” could be anyone, so it doesn't count. | 15 |
| C3 | Acceptance criteria are testable | The criteria contain none of the project's vague words, such as works or properly, so each one can be tested. | 15 |
| C4 | States a benefit | There's something after “so that”: what the user gains. | 10 |
| C5 | No vague words in the story | The title and description avoid words like fast, easy, better and user-friendly. | 10 |
| C6 | Is estimated | The story has story points. A story that isn't estimated can't be Ready. | 10 |
| C7 | Small enough | No more than the project's maximum points (8 by default). A bigger story can't be Ready. | 10 |
| C8 | One story, not two | One “I want” and no “and also”, which usually joins two features. | 5 |
| C9 | Has a description | A description of at least 20 characters. | 5 |
Scope tracking
On day one, tick the stories the team committed to (or upload them as a CSV) and lock them as the baseline; it can't be edited. A sprint picked from the backlog records every status and estimate change by itself; one built from CSVs takes a new upload as a snapshot. Stories are matched by key, so a renamed story isn't counted as removed and added, and every change goes in a dated log.
Net change
(latest points − committed points) ÷ committed points
How much bigger or smaller the sprint got.
Churn
(added + removed + re-estimated points) ÷ committed points
How much moved, even when the total didn't.
Completion
points done from the original commitment ÷ committed points
Stories added later don't count towards it.
Sprint report
One printable A4 page for the retrospective: the sprint goal and whether it was met, the metrics, why scope changed (bugs, stakeholder requests, discovered work, tech debt), the change log, and one plain sentence on whether the stories that changed scored lower before planning. Share it with stakeholders through a read-only link you can turn off at any time.
See the sample reportRefinement and Jira
- Refinement mode: one story at a time on the meeting screen, with what's missing. Fix it together, agree a size and record it in one click.
- Share the backlog: a read-only link to the unfinished stories and their scores, so people can read ahead. Turn it off at any time.
- Connect Jira Cloud: import straight from a Jira search, sync with one click, and send your edits back. Sprintwise writes to Jira only when you click Send.
Planning and trends
- Planning helper: while you pick the sprint, it shows each story's readiness, the team's usual velocity next to your total, and a warning before you commit stories that aren't Ready.
- Trends: velocity, completion, churn and readiness at planning across every sprint, with plain-English insights such as whether more Ready sprints finished more.
- Team checks: add your own Definition of Ready items; a story that fails one can't be Ready.
- Writing help: a story template, Given / When / Then starters, measurable alternatives to vague words, and ways to split big stories. No AI needed.
- Export: download the scored backlog as a CSV, or copy any story as text for Jira or Slack.
Accounts and data
- The demo runs in your browser with invented data and saves nothing.
- Sign in with GitHub to keep projects. Deleting your account deletes everything in it.
- Usage counts are anonymous: no user ID and no story text.
- Light, dark and system themes, WCAG 2.2 AA contrast, and keyboard use checked by automated tests.