Writing Better User Stories
Writing user stories is harder than you think. Trying to capture the functionality the user wants is not always simple. User stories are one of the most applicable techniques introduced by Agile and many organizations have been using them in place of stakeholder requirements in Waterfall environments because of their ease of use and relatability to their users. Getting stories right takes practice. Many user stories are too big and cannot be worked on. Some are too small adding no real value. This course helps you write effective user stories by identifying the attributes and guidelines for writing better user stories.
Earn 7 CDU/PDU for both IIBA and PMI certification
We recommend the Introduction to Business Analysis course or equivalent experience. An understanding of Agile concepts is also helpful.
Anyone that works in an Agile environment and contributes user stories, or anyone working in a different methodology who wants to move to user stories instead of traditional stakeholder requirements formats.
Register Online Today
What We Cover
- Getting to user’s real story
- What is a user story? Why does Agile use user stories?
- The format of a user story
- Qualities of a great user story
- How to write great user stories
- INVEST criteria for user stories
- Improving User Stories that don’t pass “the sniff test”
- Recognizing when a user story is not so great
- How to improve user stories
- Determine when your user story is solid enough to work on
- Providing the details for development, testing and approvals
- What is acceptance criteria?
- How is acceptance criteria developed?
- What is the difference between definition of done and acceptance criteria?
- Approaches for writing acceptance criteria (lists, bullet points, classic requirements, Gherkin)
- Sizing and Splitting Stories
- How to break down user stories to get to Minimum Viable Product (MVP)
- How to create a user story map through functional decomposition