Guide to User Story Creation
Download as PPTX, PDF•1 like•2,333 views
The document provides a quick guide to user stories, outlining the general format and benefits of user stories in product development. It emphasizes the importance of user involvement, clarity, conciseness, and completeness in crafting effective user stories, alongside offering tips for improvement and prioritization strategies. The guide also suggests including acceptance criteria and encourages the creation of a story map for better organization and clarity as requirements evolve.
Guide to User Story Creation
- 1. zQuick Guide to User Stories
- 2. zGeneral User Story Format As A (role or position), I want/need (feature/ability) So that I can (benefit of feature or ability).
- 3. z Examples As IT security, I need to limit access to information so that we can protect customer data. As a manager, I want to be able to total up sales at the end of the week so that I can produce my sales reports. As an accountant, I need access to monthly sales data so that I can keep track of expenses and profits.
- 4. z Possible Benefits of User Stories Typically easier to create and understand Helps understand things from the user’s perspective Can assist in creating a more collaborative environment Increases transparency and reduces risk
- 5. z z Make Better User Stories
- 6. z1. Include Users in Their Creation Allow the users to tell their story Have a conversation with them to gain a better understanding Summarize their story hitting the major points Ask them to review the summary and work together to get it right
- 7. z 2. Use the 3 C’s CLEAR Keep the intent CLEAR CONCISE Keep the story CONCISE COMPLETE Make the story COMPLETE
- 8. z3. Use the 3 W’s WHO WHO wants it or needs it? WHAT WHAT do they want or need? WHY WHY do they want or need it?
- 9. z4. Test the Story ASK PEOPLE IF THEY UNDERSTAND IT AND HAVE THEM EXPLAIN IT TO YOU RANDOM PEOPLE NOT INVOLVED WITH THE PROJECT MAKE GOOD TEST SUBJECTS
- 10. z5. Differentiate Between a “Want” and A “Need” THIS CAN HELP WITH PRIORITIZING PRODUCT DEVELOPMENT USE “WANT” AS A DEFAULT UNLESS YOU CAN DEFINE THE “NEED”
- 11. z6. Include User Story Acceptance Criteria With the user story there should be acceptance criteria that is required to successfully complete the task
- 12. z 7. Large Scoped Stories can be Acceptable Progressively elaborate on the stories when you need themElaborate Accept that some work items will be smaller or larger than othersAccept Focus on “Measurable” requirementsFocus
- 13. z 8. Create a Story Map Layout the user stories in a logical order As the requirements become clearer, this can help with prioritization and reducing the stories into smaller stories
- 14. z9. Focus on the Minimum Requirements WORRY ABOUT WHAT YOU NEED FIRST ADD IN THE FLAIR LATER
- 15. z z Quick Guide to User Stories Joshua Render https://agile-mercurial.com https://agile-mercurial.com/2018/08/13/9-tips-for-writing-effective-user-stories/