Writing great user stories is a core Agile skill. Clear stories reduce rework, increase predictability, and keep the team aligned on value.
A user story expresses a small piece of value from the user’s perspective — not a technical task.
As a <type of user>,
I want <some capability>,
So that <benefit/value>.
A good user story is:
AC defines the boundaries and expected behaviors of a story.
Given <context>
When <action>
Then <expected outcome>
Example 1 — Login
As a returning user,
I want to log into my account,
So that I can access my dashboard.
Example 2 — Notifications
As a project member,
I want to receive task updates,
So that I stay aware of progress.