Splitting User Stories
A brand new framework to split user stories
👋 Hey Friends
Are you ready to take your user story-splitting skills to the next level? Well, buckle up because today, we're diving deep into the BREAK-iT method, a powerful and effective way to split your large user stories into smaller, more manageable pieces.
But before we dive into BREAK-iT, here's a quick reminder about the more popular WAHZUR and T-Split methods I introduced on YouTube last year.
If you haven't watched that video, here it is for your reference:
Now let's talk about the new kid in the block, BREAK-iT.
If WAHZUR is more comprehensive (for beginners) and T-Split is more stripped down (for experts), BREAK-iT lies somewhere in the middle.
BREAK-iT is all about breaking down your user story into smaller, more manageable pieces by focusing on the
1. Big Picture,
2. Refining with User Research,
3. Exploring with "How Might We" statements,
4. Applying Personas and Scenarios, and
5. Keeping it Simple and Testable.
It's like jumping from a diving board into a pool of clarity – it's refreshing, and it feels great!
So, grab your goggles and let's dive into the BREAK-iT method!
Each technique below is divided into three sections for learning purposes:
1. The question that the Scrum Master will ask the team.
2. Team's response
3. Example user story/stories
Let's begin!
Example Large User Story (Epic):
As a frequent traveller,
I want to be able to book my flights, hotels, and rental cars all in one place on the online travel portal,
so that I can save time and have a seamless travel experience.
Split using the BREAK-iT method:
B - Begin with the Big Picture
Scrum Master question: "What's the end goal of this user story?"
Team response: "The goal is to provide a seamless travel experience by allowing users to book their flights, hotels, and rental cars all in one place."
Example User Stories:
As a frequent traveller, I want to book my flights on the online travel portal so that I can save time.
As a frequent traveller, I want to book my hotels on the online travel portal so that I can save time.
As a frequent traveller, I want to book my rental cars on the online travel portal so that I can save time.
R - Refine with User Research:
Scrum Master question: "What do we need to know about the user to make this a success?”
Team response: "We need to gather information on the user's travel habits and preferences, such as the type of flights they usually book, their preferred rental car company, and their preferred hotel amenities."
Example User Story:
As a frequent traveller, I want to provide my travel habits and preferences to the online travel portal so that I can have a personalized and seamless travel experience.
(Make a separate user story for the type of flights they usually book, their preferred rental car company, and their preferred hotel amenities.)
E - Explore needs/wants with "How Might We" statements:
Scrum Master question: "What does the user need and want?"
Team response: "The user needs an easy and convenient way to book travel."
Scrum Master question: "How might we make it happen?"
Team response: "We can make it happen by integrating with multiple travel providers, offering user-friendly interfaces, and including various travel options."
Example User Stories:
As a frequent traveller, I want the online travel portal to integrate with multiple travel providers so that I can have an easy and convenient way to book my travel.
As a frequent traveller, I want the online travel portal to offer a user-friendly interface so that I can have an easy and convenient way to book my travel.
As a frequent traveller, I want the online travel portal to include various travel options so that I can have an easy and convenient way to book my travel.
A - Apply Personas and Scenarios:
Scrum Master question: "Who are the personas affected by this user story?"
Team response: "Here are several personas that might use this feature, such as business travellers, families, and solo travellers."
Example User Stories:
As a business traveller, I want the online travel portal to accommodate my travel needs and preferences so that I can have a personalized and seamless travel experience.
As a family traveller, I want the online travel portal to accommodate my travel needs and preferences so that I can have a personalized and seamless travel experience.
As a solo traveller, I want the online travel portal to accommodate my travel needs and preferences so that I can have a personalized and seamless travel experience.
K-iT - Keep it simple and Testable:
Scrum Master question: "What's the simplest solution (MVP) that can get the job done?"
Team response: "The simplest solution is to start by integrating with one or two popular travel providers, such as airlines and hotel chains, and then gradually expanding to include more options.
This way, we can ensure a smooth and functional experience for the user while also keeping the project manageable and testable."
Example User Stories:
As a frequent traveller, I want the online travel portal to integrate with Air Canada and Air France so that I can have a smooth and functional booking experience.
As a frequent traveller, I want the online travel portal to integrate with the hotel, "Shangri-La," so that I can have a smooth and functional booking experience.
So there you have it.
One thing to keep in mind while splitting user stories is that you must focus on "simplicity" and clearly define "the user’s" goals and needs. Without this focus, the user stories will lack business value.
I hope you found this introduction to the BREAK-iT method helpful. Give it a try in your next project, and keep me posted.
- Vibhor
📌 Things I loved this Week
Book - Surely You’re Joking Mr. Feynman
Get ready for some laughs and amazing advice! This book is a compilation of tales from the life of Richard Feynman, one of the best physicists ever and the inventor of the Feynman Technique. You'll learn about productivity, how to learn better, and how to think in unique ways. It's a must-read for anyone looking to improve themselves.
✍️ Quote of the Week
“The most important thing in science is not so much to obtain new facts as to discover new ways of thinking about them.” - Sir William Lawrence Bragg
“I share things I wish I knew in the starting years of my career in the corporate world"
Vibhor Chandel
How Scrum master can guide to split technical stories and epics? Technical stories can be on Interfaces, Schedulers, Orders....