How to Split A User Story In Just 2 Steps.
HTML-код
- Опубликовано: 4 авг 2024
- It's time to split Epics and Features into right-sized User Stories.
Splitting a User Story doesn't have to be overwhelming.
In this video, I will discuss
6 fundamental techniques WAHZUR that all other techniques are variations of.
As a BONUS I will also share one easy-to-use technique that I created T-SPLIT.
After mastering T-SPLIT you won't need any other User Story Splitting technique.
In addition, this video also answers the following questions
What are User Stories
Difference between Epic, Stories, and Tasks
Benefits of splitting
Vertical vs Horizontal Splitting
Difficulties with Vertical Stories
What to do when we can't split a user story
There's a lot to come. So Stay Tuned.
00:00 - Intro
00:54 - What are User Stories
02:25 - Epics vs Stories vs Tasks
04:12 - Benefits of splitting
05:07 - How to split User Stories
11:01 - Different splitting patterns
16:35 - I created a splitting pattern
17:33 - Outro
**************************
Link to "Agile Product Planning", videos
1) How to define Product Vision
• How to create an Agile...
2) How to create a Product Roadmap (part-1)
• What Is A Product Road...
**************************
Link to GRAVITAS video
• How To Get Heard In Me...
***************
FREE DOWNLOADS:
Download my FREE Scrum Master Coaching Cards On how to resolve Conflicts as a Scrum Master here:
/ vibhorchandel_coaching...
Download my FREE Scrum Master Coaching Cards On How To Create High Performing Teams here:
/ vibhorchandel_coaching...
******************
LINKEDIN POSTS
Become part of the growing community with over 18500 professional Scrum Masters, Agile Coaches, Product Owners, and Project Managers by following me on LinkedIn, where I share Agile-related stories with practical tips, tricks, and workarounds.
linkedin.com/in/vibhorchandel
****************
If you liked this video, please give it a THUMBS UP, SUBSCRIBE, and SHARE it with your friends and colleagues.
****************
WHO AM I?
I am an Executive, Agile, and Leadership Coach based in Toronto, Canada.
WHAT DO I DO?
I Coach Agile Coaches and help Executives / Organizations attain Business Agility.
WHAT I TALK AND WRITE ABOUT?
Thoughts on Agile Transformation; Agile Coach & Scrum Master Insights & tips;
Coaching & Leadership Skills; High-Performance Teams; Agile Frameworks particularly Scrum &
Kanban.
****************
I just finished my scrum master certification, and am using an agile approach outside of software. This video really helped me figure a way to adapt the approach to my project.
Great stuff Vibhor! As a Scrum Master, I want to coach the team on breaking down user stories, so that they're committing to achievable stories within each sprint. No time like the present for practice :)
Each video I see ,I get to understand different dimensions of agile. Cannot thank you enough.. Accepted you as my agile coach..
You are doing a great job, Vibroh, thank you!
Probably the best video I've seen on the topic of splitting user stories. Well done.
This video is amazing! So much knowledge in such an easy explanation and the examples are very helpful
Had not heard of the acronym WAHZUR. Thank you for introducing it as a way to break up or write stories
Great video. I really like the speed and content of your presentations. The examples are invaluable. Keep up the great work.
I just came across your videos and I am glued. Thank you for the content
Awesome, precise and crisp
All your videos are great! I have been binge watching your videos! Thank you for creating great content thats easy to understand!!
One of the best explanation for refinement in agile space. Thanks vibhor
I love to watch and learn from your videos. This one is amazing
Great learning and thanks for sharing. Looking forward to more such videos.
Simply outstanding
Great video! thank you for the presentation and examples. it would be great if you can show us a proper backlog, how is defined with epics, user stories and tasks....
Good man with confidence. Thank you for the video! :)
im a student and while doing a project for Software Engineering i came across this video and it helps alot :D
Hi Vibhor , Thats a wonderful video and best part is the Practical Examples and not the Concept . Thank you and Well done
Great video, one of the best visual video ever seen. Thanks for the great job
Really excellent summary of the activity...
Crisp and Clear Vibhor 👍
I love your videos Vibhor!! Very informative. Please keep them coming! 👏🏽👏🏽
Thank you Tosin
Very enlightening!
short and on point vibhor... great video.
Thank you! This is super clear
Thanks a lot Vibhor! it is really simple and easy to understand
Excellent awesome!!👍👍👍👍👍👍👍
You are good Vibhor. So glad I found your channel. I just started my new scrum master role. Thank you for sharing your time and knowledge with us.
By the way you are very handsome and organized. God bless you 🙏
Wow, great video Vibhor. Was a very informative presentation with a great tone. Glad I stumbled on this video. Beautifully summarized. Thank you!
Appreciate that Keerthi, thank you
Excellent!!!
Really a valuable and informative and interesting video. Thanks for sharing such good content.
Great work sir
Thank you for helping and sharing this video
Very nice explanation. Thanks. Learnt a lot.
You have nailed it 👍
your explaination made the whole user story funda like a cake walk...casual but impactful explaination. Thanks Vibhor !
Great 👍
Excellent explanations and well made videos Vibhor .
Great stuff as always 👍
great content! Graphics are on point and the body of the videos is super relevant! thank you for the hard work!!!!!
Appreciate you Liz, thanks alot
very clear!! thanks
Thank your for Information it’s too much helpful
Mind Blown!
Thank you so much, this video clear so many doubts
Awesome content, its very helpful. Thank you Vibhor.
Wonderful content.
Looking forward to the tutorial series on “effective user stories”
Excellent content..... very informative
💯superb video !
This is definitely really good content! I would be interested in connecting to learn more tips and trick for Agile.
Excellent!
I enjoyed this. Very succinct with a lot of information conveyed. I agreed with 80% of this which is a record: I don't even agree with myself that mych.
Great Video Vibhor .. thank you !!
very good explanations , thank you
Its very helpfull thankyou
Valuable information
this is informative, although you have a slightly different approach than others, it does make sense what you are talking about. Thumbs up.
Thank you for making it look easy
Thank you so much for such deep knowledge sharing. a big thx
Thank you Mariem
Hey Vibhor, Very well explained 👌
great explanation sir !
Very good synopsis!
This is a really useful video and I like the analogy of the slice of cake.
Great session. I will definitely try vertical slicing, knowing that my teams are committed frontend and backend developers and are so used to horizontal approach.
Vertical slice is hard, but worth the effort.
Thank you from Thailand
Great video👍
superb
fantastic
Awesome video, the content was really good.
Thank you Raghu
"JUST BE AGILE" 🙌🙏👌
Loved the video.. one of the best videos I have watched 🤝🤝🤝
Please let me know on how to further collaborate for personal learning/consultancy/brainstorming. Will connect with you
Hi, Vibhor thank you for your video very interesting. In the teams, I am following I often have the "Horizontally issue" (that you well explained). This is because as you said,, there are silos (Analysts, Developers, Testers) and often they aren't able to do all three tasks in one sprint.
In this case, what is your suggestion? Let them divide the US horizontally or maintain a single story for more than one sprint or another.
Very well done man. Great job. You should charge for these kinda vids.
Nice video! but I have a question: when talking about acceptance criteria you create 3 user stories which do not seem very independent to me. what's the deal with the independency criterium for user stories then?
Ur agile Guru sir, thank you for simplifying and helping people like me. Do u also coach one on one??
liked it thank you. any inputs on how to roll up weights to stories with tasks.
Would you be able to create a video on creating User Stories / EPICs on Dashboarding projects (like Qlik Sense, Tableau and Power BI) where it involved everything from Data Source to ETL and then to the Dashboards & Maintenance.
I agree with you on the point whereby we shouldn't split the stories horizontally but there has been very little examples online and even on RUclips on how you can do that vertically in the field of Dashboard Development. Most are usually related to Software Development. And for Dashboard Development, it is usually the ETL which takes up the bulk of the time (and Data Validation after modelling them to check if the process is valid/right).
I have recently been in a team who did just that: Split by layer. Using tasks. Since we had dedicated frontend and backend developers it was hard to coordinate - and we struggled to close our User Stories.
In some ways they were not real User Stories either, but renditions of the Requirements.
I am in the same situation
I wish I was In the same situation 😊
I have the same problem on my team, but we still split by vertical slices.
Frontend (FE) devs work on the FE tasks, backend (BE) devs on the backend and then we integrate.
It's not ideal but, nevertheless, we deliver a full vertical slice, not a layer.
@@guybrushthreepwood2910 It depends on what the team is used to and if they are comfortable taking command and organize it the way it works best or them as a team. There is a problem when the team members are used to do tickets rather than features. And some environments sadly treat features as tickets to be completed once they have been planned. There is no replanning ever.
@@marna_li Yes, the most difficult thing to change is the culture and what people have been used to doing for a long time.
You said "some environments sadly treat features as tickets to be completed once they have been planned".
I'm not sure I understood this or what you are pointing with it. Are you talking about how they behave more like "bots" to get the job done and they don't take the time to analyze and perhaps split the stories into multiple other ones?
Hi Vibhor,
You have not been posting videos for over a long period.Hope all is well with you.
I miss coming here to study through your ever detailed , informative, clear, and quality videos .
Hi Vibhor, thanks for your Great explained series. Helped me and my team a lot. In 14:00 you have a happy path, which I assume that it's from the last approach(Acceptance Criteria). Am I correct, or it's the Happy story for the "user log in"?
I would like to hear more about why you've found that only 35% of User Stories fit the INVEST criteria; and how a Scrum Master can be sure they are appropriately and consistently applying the INVEST criteria.
Great content Vibhor! Am I mistaken to assume that your 'T-Split' technique splits stories by Scenarios (breath) and Workflow requirements (depth)? Cheers!
Great Content!! Thank you for sharing.
I just wanna say, that the "T Split" part was really confusing, It didn't make any logical sense to me. I think many others have also commented on it. if you have some time then it would be great if you can clarify this method here or make a detailed video around it.
Great explanation, Thank you very much for creating this tutorial series.
When will you be releasing seperate tutorial series on "User stories"?
I am seriously delayed on this. Thanks for inquiring.
@@VibhorChandel You are awesome, please do it
Very insightful. Can I please get more help on splitting user stories and acceptance criteria.
Hi Vibhor, Your content is really valuable and helped me in understanding & implementing.
Is there any technique or approach for Acceptance Criteria?
Hi Mohit, I have a technique that I will be sharing in my newsletter soon.
hey Vibhor, I noticed you didn't talk about the Moscow technique, what's your take on it ?
great info, impressive... could u show me, how i can download it.pls tell
In the T-Split example, we have these 2 cases:
S1) breadth: "As a traveller, I can pay using my credit card"
S2) depth: "As a traveller, to pay I need to enter my card details"
How can S1 be implemented without S2? In other words, what would we be testing in S1?
Hi Vibhor I have a question, in case that you split the story by Workflow as your example and I just release 2 stories are: As A Customer I can log into my account, So I don't have to enter my shipping information every time and As a Customer, I receive a confirmation email with my order, So I have proof of my order. In this case, we deliver 2 stories but the second story does not bring value to customers because they need to wait until the remaining stories are completed to fulfill the buy flow. In this case, could I merge it into one?
Is that printed text editor at 10:17 🤣?
Good videos by the way, thank you.
I would like to hear more on vertical split of US, how a US1 & US2 are so independent to be delivery separately? In practice you wouldn't more than 20% developers which are full stack.
Hi Vibhor, great video btw, have a question wrt WAHZUR, do you need to apply *all* of these for each user story, or simply select most appropritate one and apply it. Thanks!
You just apply what you need. Wahzur is a checklist so you pass through all possible ways of splitting.
I am a Product Owner trying to apply agile methods within a Data Analytics Squad whose responsibility is to perform all the tasks of ingesting, cleaning, transforming and delivering information to the business areas. I have not been able to break down the stories as I feel the business would like and deliver value at the end of a sprint. Do you have any references from the data and analytics area that can be applied to try a more agile approach?
Thanks for your videos.. they are amazing!!!!
Try 5 why's.
Awesome content. Do you plan to release a separate series on user stories ?
Yes will be published in the new year
@@VibhorChandel thank you for the reply. Look forward to it
Hi, Can you help me what is feature in Agile, where doess it fit in agile ?
I have a question regarding enablers. Context here is team will say they need to come up with design and those are enablers. Only once the design is there they can develop. Can you share some detailed insight of what really is an enabler and what is not.
Hi. Great video. Friendly heads up, you skipped the V in INVEST while stating what each letter means.
My po created only one userstory for over all developementand asked me to create subtask for every activity in development...is it good?i thought of creating usersstories for ddl/dml and procedure scripts and testing....if we create subtasks then how to maintain and move to very sprint and how to estimate... please give me insight on this ..code is bigquery so we don't have ui