User story writing captures product requirements from the perspective of the end user that derives a valuable outcome from this requirement being delivered.
It must have a short meaningful title, value statement, and acceptance criteria, but may also have a description or other supporting business and technical insights that helps the team to estimate and deliver the requirements.
Apply INVEST principle to improve focus on value outcomes
👥Who
User story writing is undertaken primarily by someone acting in the role of product manager. During and post refinement other team members may contribute to the user story.
🛠 Running the technique
The user story title should reflect the valuable outcome, and not the intermediate steps. Try to use a single active verb and object. e.g. Display current personal details
The value statement should take the form of … AS A (describe the end user who has a need) I WANT TO (the action to take) SO THAT (the benefit/ valuable outcome achieved)
Write a description of what goods looks like when this user story is delivered, if this may help refinement with team members
Ensure the user story adheres to the INVEST principle: Independent, Negotiable, Valuable, Estimable, Small, Testable
Draft the acceptance criteria that needs to be satisfied. Please refer to the BDD technique guide for further detail.
Engage with relevant team members to refine and estimate.
No Comments