How to write easily understandable user stories
•
1 like•281 views
This document provides an overview of best practices for writing user stories, including how to write user stories, define test cases and acceptance criteria, report bugs, define tasks, understand what makes a user story ready, and use JIRA effectively. It covers topics like using the "As a, I want, So I can" format for user stories, providing test cases in a "Given, When, Then, I Expect" structure, defining acceptance criteria, reporting bugs with steps to reproduce and expected vs. actual behavior, understanding what makes a user story independent, estimatable, negotiable, small, valuable and testable, and tips for using JIRA like markup, versions, and alphabetizing epics.
Recommended
Recommended
More Related Content
Similar to How to write easily understandable user stories
Similar to How to write easily understandable user stories (20)
Recently uploaded
Recently uploaded (20)
How to write easily understandable user stories
- 1. © AND Digital 2017 Writing easily understandable stories
- 2. © AND Digital 2017 1. User story 2. Test cases 3. Acceptance criteria 4. Reporting bugs 5. Tasks 6. Definition of Ready 7. JIRA Agenda
- 3. © AND Digital 2017 Brainstorm What makes a bad user story? Exercise
- 4. © AND Digital 2017 The ‘user’ story... As a... I want a... So I can Member of the library An online account Change how long I have borrowed a book for without going back into the library User Feature Benefit
- 5. © AND Digital 2017 Test cases GIVEN WHEN THEN I EXPECT I am on the Cogent content site I click the portal link on a specific journal To be taken to the RP with my journal pre-selected Initial conditions Action Result
- 6. © AND Digital 2017 How to report a bug... Steps to reproduce Expected Behaviour Actual Behaviour Go to the Cogent content site and click Login I’m taken to the ORCiD login page It hangs and I get a blank screen Initial conditions Action Result https://www.chiark.greenend.org.uk/~sgtatham/bugs.html
- 7. © AND Digital 2017 Acceptance criteria
- 8. © AND Digital 2017 Tasks, Investigations and UX Feedback + Iteration
- 9. © AND Digital 2017 Definition of Ready - INVEST Independent Estimatable Negotiable Small Valuable Testable https://en.wikipedia.org/wiki/INVEST_(mnemonic)
- 10. © AND Digital 2017 Version 2 Sprint Version 1 Three JIRA tips... 1. Use JIRA markup https://jira.atlassian.com/secure/WikiRend ererHelpAction.jspa?section=texteffects 2. Use versions to rationalise your backlog 3. Alphabetise your epics
- 11. © AND Digital 2017 The tyranny of JIRA... 1 user story ≠ 1 JIRA task
- 12. © AND Digital 2017 Write a user story based on these guidelines for: 1. A navigation menu 2. A system monitoring tool 3. Server logs Exercise
- 13. © AND Digital 2017 1. User story 2. Test cases 3. Acceptance criteria 4. Reporting bugs 5. Tasks 6. Definition of Ready 7. JIRA tips Recap
- 14. © AND Digital 2017 Additional reading material 1. AND Digital blog on what makes a good user story - https://and.digital/blog/learning-at-work-week-1-what-makes-a-good-user-story/ 2. Government Digital service guide to good user stories - https://www.gov.uk/service-manual/agile-delivery/writing-user-stories 3. How to report a bug effectively - https://www.chiark.greenend.org.uk/~sgtatham/bugs.html 4. Example Definitions of Ready and Done - https://docs.google.com/presentation/d/1rZGWVHaXGNLH8Dvh0k3ic7CInw3ZIMwTpeGegPNvdGM/e dit#slide=id.g22aeec317f_0_7
- 15. © AND Digital 2017 Over Out