Free BA tool

User story builder with INVEST checklist

Write a clear user story in the "As a, I want to, so that" format, check it against INVEST and start your acceptance criteria.

A user story describes a small piece of value from the point of view of the person who receives it. The usual format is As a [role], I want to [goal], so that [benefit]. The role says who, the goal says what they want to do and the benefit says why it matters. The "so that" part is the one most often skipped, and it is the part that lets a team judge value and negotiate the solution.

INVEST is a checklist for a good story: Independent, Negotiable, Valuable, Estimable, Small and Testable. Acceptance criteria then make the story testable by stating, in Given/When/Then form, what must be true for the story to be done.

How to use it

Type who needs the change in As a, for example "returning customer". Use a real role, not "user" or "system".
Type the action in I want to and the reason in So that. The story updates as you type.
Work through the INVEST checklist. Read any hint, decide whether it applies and tick the items you are satisfied with.
Edit the Given/When/Then scaffolds: replace every [bracketed] placeholder with real data, numbers and messages.
Copy the result or download it as a Markdown (.md) file for Jira, Confluence or your notes.

User story builder

Private by design. What you type stays in your browser. Nothing is sent to BA Mentorship. Nothing is saved either: copy or download your work before you close the tab.

Your story

As a… (who needs this)

I want to… (what they want to do)

So that… (why it matters to them)

Your user story

Fill in the three fields to see your story.

INVEST checklist

Tick each quality when you are satisfied. Automatic hints appear when the wording suggests a problem; they are prompts, not verdicts.

I: Independent. The story can be built, tested and released without waiting for another story in the same sprint. Could the team deliver this story on its own?
N: Negotiable. It states the need, not a fixed design, so the team can discuss how to meet it. Does it leave room to agree the solution with the team?
V: Valuable. The "so that" names a benefit a user or the business actually cares about. Would the user notice and care if this shipped?
E: Estimable. The team understands it well enough to size it. Unknowns usually mean a question to answer first. Could the team give a rough size today?
S: Small. It fits comfortably in one sprint. One goal per story is a good rule of thumb. Can it be finished in a few days of work?
T: Testable. Someone can write a pass or fail check for it. Vague words make a story hard to test. Can you write at least one Given/When/Then for it?

Acceptance criteria (edit freely)

Scaffolds appear when your story is complete. Replace every [bracketed] placeholder with real, measurable details.

Questions and explanations

What makes a good user story?

A good story names a real person, one goal and a benefit that person would recognise. "As a returning customer, I want to reorder a previous order in one step, so that I can restock household items without searching again" is clear about who, what and why. "As a user, I want a reorder button" names a design and no benefit, which leaves the team guessing.

Why does the tool strip words like "I want to" from my input?

Many people type the template words into the fields. The builder removes a leading "As a", "I want to" or "so that" so the story does not repeat them. Check the result reads naturally; you can always edit it after copying.

Are the INVEST hints a score?

No. The hints come from simple wording rules, such as spotting "and" in the goal (a sign the story may be two stories) or a vague word like "fast" (hard to test). A story can be fine even with a hint, and a story with no hints can still be too large. Use them as prompts for a conversation with your team.

How many acceptance criteria should a story have?

Enough to describe the main path, the important alternatives and any rule that could be misunderstood. For a small story that is often three to six scenarios. If you need many more, the story is probably too big and should be split.

Is my story saved anywhere?

No. The builder runs in your browser only and keeps nothing after you close or reload the page. Copy or download your work before you leave.

These tools are free practice aids from BA Mentorship. They use simple, transparent rules, not AI, and they do not assess or certify your work. BA Mentorship is not affiliated with IIBA, PMI or IREB.