
In this lecture we'll get a short introduction to what a User Story is, and how anyone can make a User Story themselves.
We'll also talk about roles and context in User Stories, and the exceptions to the rules of User Story writing.
Why was User Stories created in the first place? How did User Stories replace the regular Requirement Specification from the waterfall method?
User Stories are really short, so how do we communicate basic requirements so we know when the User Story is done? This is where Acceptance Criteria comes in.
What is the definition of done, and how does it compare to Acceptance Criteria in User Stories?
Learn what INVEST stands for and how it can help you write the best User Stories possible!
Why should User Stories be small? Why are we not just making 1 big User Story for our whole project?
What's the perfect size for a User Story? Does one size fit all?
Watch out for the waterfall !
Before we move on to User Story splitting, let's talk briefly about the Lean Startup Methodology.
Every project starts up with 1 big User Story, that has a ton of User Stories hidden underneath! Let's see how we would go about splitting this!
Hello and welcome to the User Stories course!
In this course you will learn in a relaxed and fun manner how to write basic user stories, what the 3 C's in User Stories are. You'll learn about INVEST and User Story splitting.
You're also going to learn how User Story splitting ties in with the Lean Startup Methodology and how to launch new projects as soon as possible with User Story Splitting!
I hope you will enjoy my course, and if you're looking for any explanations feel free to message me any time!