
Introduction
The parts of a good user story, what not to forget.
This is an example of a good user story. Relatable to the real world.
A short discussion about the differences between a requirement and a user story. Also the differences in case of Agile and waterfall are raised.
How to proceed when you need to create a user story. A step by step approach.
The principle of INVEST in user stories.
A small exercise on creating a user case for a problem statement. It also includes a common mistake and how to deal with this.
Another exercise on how to compile a user story.
A small recap and a word from your teacher.
This is a short recap course that explains the structure of a user story and gives a step-by-step process on how to create a good user story.
Following these steps and thinking about each component, you will be able to write comprehensible user stories that can be interpreted by all stakeholders.
This course is intentionally short. I don't want to explain too much unnecessary information, only the necessary fundamentals.
It covers the components of a good user story, it delivers an example of a user story, and discuss it, and the last part are two exercises where we go over the creation of two user stories for a problem ourselves.
This course is complementary to my general Functional analyses course and my course about writing documentation for IT and software development.
The course describes the parts of a good user story, after that it will show this in an existing user story. The next part will cover briefly the similarities between a user story and a requirement, and we conclude with an exercise on how to create a user story from a given problem statement.
This course is a good starter for writing user stories for aspiring analysts, but it can also be studied by developers and testers as they often need to write or edit stories themselves.