“As a user, I want…” is where most stories start. It is also where most of them go wrong.
QPulse scores any user story or acceptance criteria against INVEST and SMART, tells you exactly which criterion it fails, and rewrites it for you. No more finding out in sprint planning.
As a user, I want to log in so that I can use the app.
4 / 10- Valuable: “use the app” is not a real benefit.
- Testable: nothing here can become a test case.
As a returning customer, I want to sign in with my email and password so that I can see my saved orders.
9 / 10- Specific persona, concrete outcome, Given/When/Then attached.
Everyone approved the story. Nobody agreed on it.
The story passed refinement. Three people gave a thumbs up. Then the developer builds one thing, QA tests another, and the BA meant a third. Now you are four days into the sprint arguing about what “log in” was supposed to include.
The story was never the problem. It was vague, and vague reads as agreement. A story that isn’t clear doesn’t look unclear. It looks exactly like everyone agreeing, right up until someone writes the code.
- A developer starts building and stops within an hour to ask what the story actually meant
- QA writes test cases and finds there is nothing testable in the acceptance criteria
- The BA gets pulled into a call to explain a story they wrote nine days ago
User story INVEST criteria, scored line by line
INVEST stands for Independent, Negotiable, Valuable, Estimable, Small, and Testable. It has been the standard for good stories since Bill Wake wrote the INVEST criteria in 2003. Every agile coach can recite them. Almost no team applies them consistently, because checking forty stories by hand in one refinement session is not realistic.
QPulse checks your story against INVEST in seconds and shows you the result letter by letter, not as one vague number. It also scores your acceptance criteria against SMART, so you see how solid the story is and how clear its conditions are.
Independent
Can this ship on its own, or is it quietly waiting on three other tickets?
Negotiable
Does it describe an outcome, or has someone already written the solution into it?
Valuable
Can you name who is better off when this ships? If the answer is "the backend," flag it.
Estimable
Is there enough here to size, or will the team guess and call it a five?
Small
Will this fit in a sprint, or is it an epic wearing a story costume?
Testable
Can QA write a passing and a failing case from this? If not, it is not done, it is just closed.
An example user story, scored and rewritten
Here is a real user story example of the kind that passes refinement every day.
Before
Score 4 / 10“As a user, I want to be able to log in so that I can use the app.”
- Independent: Pass
- Negotiable: Pass
- Valuable: Fail. “Use the app” is not a real benefit.
- Estimable: Fail. No auth method, error states, or session handling.
- Small: Pass
- Testable: Fail. Nothing here turns into a test case.
After
Score 9 / 10“As a returning customer, I want to sign in with my email and password so that I can see my saved orders without re entering my details.”
Given a registered customer with a verified email
When they submit a correct email and password
Then they land on the orders page with their saved order history visible
Given a registered customer
When they submit an incorrect password three times
Then the account locks for fifteen minutes and a reset link is emailed
Same feature. One of them starts an argument in sprint planning. The other one gets built. QPulse writes that second version for you.
Three steps, no setup
Paste
Drop in a user story and its acceptance criteria. Or just the story, if you haven’t written the criteria yet.
Score
QPulse checks it against INVEST and SMART and shows which criteria failed and why.
Rewrite
Take the suggested version, or edit it and re score until it clears.
Skipped the acceptance criteria? QPulse writes them for you.
A story with no acceptance criteria at all is common, and it’s what most “story generator” tools quietly ignore. Leave that field blank in QPulse and it drafts two scenarios for you in Given/When/Then form: one where things go right, and one where they don’t. That way your story is testable even before you’ve written a single test case.
You paste
“As a shopper, I want to filter search results by price.” Acceptance criteria left blank.
QPulse generates
Given I am a shopper in a valid starting state
When I perform the primary action described in the story
Then the system completes the action and confirms success clearly, with a defined, measurable threshold
Given I am a shopper providing invalid or incomplete input
When I attempt the primary action
Then the system rejects the action and explains what needs to be corrected, with a defined, measurable threshold
Already have acceptance criteria written? Paste them in instead and QPulse scores and rewrites what you wrote rather than replacing it.
Built for the people who pay for a bad story
Business analysts
Stop defending stories in a call nine days after you wrote them. Catch the gap before it ships to the board.
QA engineers
Get acceptance criteria you can actually build test cases from, without chasing the author for a week.
Product engineers
Know before you branch whether the ticket has enough in it to finish.
Developers
Spot the epic pretending to be a story before it eats your sprint.
Requirements quality is measurable. Most teams just never measure it.
Every other part of your delivery pipeline has a gate. Code gets reviewed. Builds get tested. Deploys get checked. The requirement, which everything else depends on, gets waved through in a thirty minute meeting.
QPulse gives that requirement a number. Not to gatekeep your team, but so “this story isn’t ready” stops being one person’s opinion and becomes something you can point at. That’s the same standard behind the Definition of Ready in agile.
Score your next story before your next refinement
Bring one story. The one you already suspect is vague. QPulse will tell you in nine seconds whether you were right.
Free account, no credit card. Your scores save automatically so you can watch your backlog improve sprint over sprint.
Already have an account? Sign in
Questions about your backlog? Ask a human.
QPulse is built by TestMetry, which has spent years on software testing and test automation. If you want to talk about story quality in your team, or you hit something the tool got wrong, get in touch.
Usually a reply within one working day.