
Before you start writing User Stories. You should understand what problem they solve, and how it is supposed to work.
User Story wants to ensure product teams can build what is meaningful for the end-users.
Don't confuse User Stories with a requirement tool. On the contrary, User Stories is a tool to foster collaboration and ensure we never forget the most important part of any product & service: the end-user.
Before you jump into writing User Stories. You should understand what is the mindset behind it.
Pictures unfold stories. Great User Stories are just the same, when you look at them, a story unfolds.
It's time for you to know what User Stories are not.
Misunderstanding User Stories will lead you to frustrations. It's time to clarify the misconceptions.
User Stories is meant to be simple. Let's not overcomplicated it.
It's never about writing better User Stories. It's always about fostering collaboration.
What are the ingredient to be successful with User Stories?
The User Story should fit a card. Great User Stories are no more than an invitation for a good conversation.
The most important part of User Stories is the conversation. Building shared understanding is the goal. It's never about keeping requirements.
As you build the shared understanding with the team. You can define the Acceptance Criteria, but never before.
What will lead you to master User Stories?
User Stories are simple, yet often confused. The mindset behind is vital to thrive.
Evaluating if your User Stories will lead to great conversations.
To have better conversations. You should start with the why, not the what or the how.
Be careful. User Stories is neither suitable for everything nor it's mandatory for everything.
If you are overthinking while writing User Stories, probably you made the wrong choice.
User Stories are always written from the Users Perspective.
Maybe you should reflect on reporting bugs with User Stories. There are better approaches for that.
It's always about the problem to solve instead of a solution to implement.
Splitting User Stories properly is crucial.
Everything is a User Story. The difference is on the size.
What are the secrets to split User Stories properly?
A practical example of splitting a User Story.
Another practical example of splitting a User Story.
Now it's your time to practice writing User Stories. I've got a challenge for you.
What are the different estimation techniques?
How to estimate with Story Points
How to estimate with T-Shirt size techniques
How to estimate with time material
How to estimate with Planning Poker
How to estimate with the Estimation Game
Until you have clarity on the big picture, you may fail to advance as fast as you should.
Working solely with User Stories might lead you on becoming a feature factory team. You need to have the product overview on your mind.
How can User Story Mapping cover the User Stories' gaps?
User Story Mapping explained in a single picture.
What are ingredients to thrive with User Story Mapping?
Don't let myths hold you back from using User Story Mapping.
Collaboration is vital to succeed with User Stories.
Every good User Story Mapping start by defining the User Roles.
Once you have defined the User Roles, it's time to create the narrative flow. Also, known as the User Journey.
What do the Users do?
To finish the User Story Mapping, it's essential to collaborate with multiple disciplines.
As the User Story Mapping gains a shape. You should prioritise what to focus on. But first you should define a goal to pursue, without it, everything is arguably a priority.
Now it's your time to practice. I've got a challenge for you. I hope you enjoy it.
Which books should you read to advance or mindset on building successful products?
I imagine you wonder, why do you have to write User Stories? What's in it it for you? You wonder how User Stories will help you create more valuable products, and you find no answer for that. I feel you, I had the same.
Here's what you may find with product teams:
Frustration because they face a hard time to build what really matters. Some common anti-patterns you will face in Product Teams:
Feature maximizers
Stakeholders' puppets
Firefighters
This scenario annoys you and many people. Nobody wants to be trapped.
It's time to move from pleasing stakeholders to build product that changes people's lives for the better. Over the years I learned the power of combining User Stories and User Story mapping. Let me help you do the following:
Avoid waste by not building irrelevant features
Maximize the outcome by solving the end-users' real problems
Increase the team members' engagement through intensive collaboration
You won't learn how to write better User Stories in this course. You will learn how to use User Stories to foster collaboration and build meaningful products to the end-users. You can expect to know how to apply the following by the end of this course:
How to maximize the benefits of User Story and User Story Mapping
Escape from the traps awaiting you
Master the art of focusing on what matters the most and avoid distractions
If you want to your teams to love how you provide clarity and set them in a valuable direction, join this course and let me help you get there.