Probably the best video I've seen on the topic of splitting user stories. Well done.
@TristanBailey
6 ай бұрын
Had not heard of the acronym WAHZUR. Thank you for introducing it as a way to break up or write stories
@KishitaVariya
6 күн бұрын
There is so much value in this video! most videos out there are only theoritical knowledge, but this video actually brings clarity on how should I actually approach user story writing.
@hemabrijesh6710
Жыл бұрын
Each video I see ,I get to understand different dimensions of agile. Cannot thank you enough.. Accepted you as my agile coach..
@Ask_LyRc
2 жыл бұрын
im a student and while doing a project for Software Engineering i came across this video and it helps alot :D
@rgsudusky
Ай бұрын
All I can say is this video convinced me to Subscribe.
@ankursharma7812
Жыл бұрын
Awesome, precise and crisp
@damarisfozaopowell3137
2 жыл бұрын
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 🙏
@saranshmehra8577
Жыл бұрын
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.
@Rick1972mx
2 жыл бұрын
Great video, one of the best visual video ever seen. Thanks for the great job
@CodegraphersBD
Жыл бұрын
this is informative, although you have a slightly different approach than others, it does make sense what you are talking about. Thumbs up.
@orelstudies
2 ай бұрын
This video is amazing! So much knowledge in such an easy explanation and the examples are very helpful
@shubhrasharma4189
2 жыл бұрын
your explaination made the whole user story funda like a cake walk...casual but impactful explaination. Thanks Vibhor !
@CindyAlexius
2 жыл бұрын
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 :)
@womanlikeme33
2 жыл бұрын
I just came across your videos and I am glued. Thank you for the content
@igorsk19
2 жыл бұрын
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....
@krishnachaitanya7712
2 жыл бұрын
Hi Vibhor , Thats a wonderful video and best part is the Practical Examples and not the Concept . Thank you and Well done
@tamlandipper29
24 күн бұрын
I'm really interested in expanding on your point by explicitly linking stories to a scenario then evaluating the probability and impact of the scenario.
@VibhorChandel
9 күн бұрын
Coming up
@elizabethkengne2928
Жыл бұрын
Excellent content..... very informative
@2Black4yall
2 жыл бұрын
"JUST BE AGILE" 🙌🙏👌
@ramachandusharma5867
2 жыл бұрын
Really a valuable and informative and interesting video. Thanks for sharing such good content.
@IshaLuthra-yt6ug
Жыл бұрын
I love to watch and learn from your videos. This one is amazing
@firozkhaleel8461
2 жыл бұрын
Thank you for helping and sharing this video
@rajkumarmfsr
3 жыл бұрын
One of the best explanation for refinement in agile space. Thanks vibhor
@veronicagola9901
Жыл бұрын
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.
@tonyplank
Жыл бұрын
Vertical slice is hard, but worth the effort.
@vikrama2189
Жыл бұрын
Excellent explanations and well made videos Vibhor .
@tonyplank
Жыл бұрын
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.
@raymondlynch660
3 жыл бұрын
Really excellent summary of the activity...
@matisseterdam
6 ай бұрын
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!
@VibhorChandel
6 ай бұрын
You just apply what you need. Wahzur is a checklist so you pass through all possible ways of splitting.
@Sina-sd6qp
2 жыл бұрын
Good man with confidence. Thank you for the video! :)
@I_want_to_break-free
2 жыл бұрын
Thank you from Thailand
@raev4u
2 жыл бұрын
Loved the video.. one of the best videos I have watched 🤝🤝🤝
@raev4u
2 жыл бұрын
Please let me know on how to further collaborate for personal learning/consultancy/brainstorming. Will connect with you
@keerthipt736
2 жыл бұрын
Wow, great video Vibhor. Was a very informative presentation with a great tone. Glad I stumbled on this video. Beautifully summarized. Thank you!
@VibhorChandel
2 жыл бұрын
Appreciate that Keerthi, thank you
@lizflint3580
2 жыл бұрын
great content! Graphics are on point and the body of the videos is super relevant! thank you for the hard work!!!!!
@VibhorChandel
2 жыл бұрын
Appreciate you Liz, thanks alot
@atul.singh008
2 жыл бұрын
Great learning and thanks for sharing. Looking forward to more such videos.
@MrLwliang
2 жыл бұрын
Thank you! This is super clear
@TheMyriade
2 жыл бұрын
Thank you so much for such deep knowledge sharing. a big thx
@VibhorChandel
2 жыл бұрын
Thank you Mariem
@pargunandurairaj2377
3 жыл бұрын
short and on point vibhor... great video.
@thx5001
Жыл бұрын
This is a really useful video and I like the analogy of the slice of cake.
@chiarabozzacchi2299
3 жыл бұрын
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?
@stevenicolas2431
2 жыл бұрын
Its very helpfull thankyou
@mayazansari6135
2 жыл бұрын
Thank you so much, this video clear so many doubts
@ahealthyyouwithdoctornew9749
2 жыл бұрын
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.
@muhammaddevanozaidan6837
Жыл бұрын
very good explanations , thank you
@reshmach3212
3 жыл бұрын
Ur agile Guru sir, thank you for simplifying and helping people like me. Do u also coach one on one??
@vishwanathauti644
2 жыл бұрын
Great work sir
@menakaramasamy8936
3 жыл бұрын
Very nice explanation. Thanks. Learnt a lot.
@saketsharma653
4 ай бұрын
Thank your for Information it’s too much helpful
@GauravSharma-oe3gt
2 жыл бұрын
Awesome content, its very helpful. Thank you Vibhor.
@rakshakohlinarola-ho4vw
5 ай бұрын
great info, impressive... could u show me, how i can download it.pls tell
@piotrlanger7744
3 жыл бұрын
You are doing a great job, Vibroh, thank you!
@stressboy4326
Жыл бұрын
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 KZitem 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).
@benjwal
Жыл бұрын
liked it thank you. any inputs on how to roll up weights to stories with tasks.
@anthonyifedirah9672
2 жыл бұрын
Thank you for making it look easy
@OluwatosinOladipo-pj4ue
Жыл бұрын
Very insightful. Can I please get more help on splitting user stories and acceptance criteria.
@CJModestoful
2 жыл бұрын
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.
@volvorin6891
Жыл бұрын
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.
@Deepzdone
3 жыл бұрын
Crisp and Clear Vibhor 👍
@karimk9448
3 ай бұрын
Very well done man. Great job. You should charge for these kinda vids.
@blessed3830
2 жыл бұрын
All your videos are great! I have been binge watching your videos! Thank you for creating great content thats easy to understand!!
@martin82844
Жыл бұрын
I am still interested in the cake scenario. If you are building a new system, setting up everything is not possible in 1 sprint to create a slice of cake. And we can do pair programming, still it won't be delivered in 1 sprint. So what we do then?
@guybrushthreepwood2910
Жыл бұрын
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?
@sanjeevsadasheorao5294
3 жыл бұрын
Simply outstanding
@mohitkhandelwal4759
Жыл бұрын
Hi Vibhor, Your content is really valuable and helped me in understanding & implementing. Is there any technique or approach for Acceptance Criteria?
@VibhorChandel
Жыл бұрын
Hi Mohit, I have a technique that I will be sharing in my newsletter soon.
@agilemindset247
Жыл бұрын
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 .
@pricesmith1793
3 жыл бұрын
Looking forward to the tutorial series on “effective user stories”
@janka2474
2 жыл бұрын
Great 👍
@TosinOlajide
2 жыл бұрын
I love your videos Vibhor!! Very informative. Please keep them coming! 👏🏽👏🏽
@VibhorChandel
2 жыл бұрын
Thank you Tosin
@MLaurenavicius
3 жыл бұрын
Very enlightening!
@samtimy
3 жыл бұрын
Thanks a lot Vibhor! it is really simple and easy to understand
@marna_li
2 жыл бұрын
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.
@teonaloving7654
Жыл бұрын
I am in the same situation
@jojee.k
Жыл бұрын
I wish I was In the same situation 😊
@guybrushthreepwood2910
Жыл бұрын
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.
@marna_li
Жыл бұрын
@@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.
@guybrushthreepwood2910
Жыл бұрын
@@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?
@firozkhaleel8461
2 жыл бұрын
Valuable information
@mytruereviewsandgenuineinf1131
2 жыл бұрын
Great Video Vibhor .. thank you !!
@jodajo21
Жыл бұрын
Very good synopsis!
@rajeshphilip1471
Жыл бұрын
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.
@tomvance3914
7 ай бұрын
Mind Blown!
@TheImmaculateJ
2 жыл бұрын
Hi. Great video. Friendly heads up, you skipped the V in INVEST while stating what each letter means.
@dougtalbot193
3 жыл бұрын
Great video. I really like the speed and content of your presentations. The examples are invaluable. Keep up the great work.
@priyankatapare5278
5 ай бұрын
great explanation sir !
@stefanoercole6569
2 жыл бұрын
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.
@Loc_87cdp
2 жыл бұрын
very clear!! thanks
@SrividyaNatarajan
3 жыл бұрын
Excellent awesome!!👍👍👍👍👍👍👍
@raghukm5526
2 жыл бұрын
Awesome video, the content was really good.
@VibhorChandel
2 жыл бұрын
Thank you Raghu
@anbuarasi8110
3 жыл бұрын
You have nailed it 👍
@UmairKhan-hc2ql
11 ай бұрын
Great stuff as always 👍
@BibliLit
Жыл бұрын
💯superb video !
@taherkayamkhani8214
2 жыл бұрын
Excellent!
@latoyascott802
2 жыл бұрын
This is definitely really good content! I would be interested in connecting to learn more tips and trick for Agile.
@sankalpkhare264
3 ай бұрын
Do we prioritize epic or user story ?? And how we prioritize user story for story map??
@greatladyp6632
2 жыл бұрын
hey Vibhor, I noticed you didn't talk about the Moscow technique, what's your take on it ?
@hemantdhakate
3 жыл бұрын
Excellent!!!
@pazande
2 жыл бұрын
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!!!!
@VibhorChandel
2 жыл бұрын
Try 5 why's.
@alokaggarwal6985
2 ай бұрын
superb
@parthkumarpatel2775
2 жыл бұрын
Great explanation, Thank you very much for creating this tutorial series. When will you be releasing seperate tutorial series on "User stories"?
@VibhorChandel
2 жыл бұрын
I am seriously delayed on this. Thanks for inquiring.
@saishekarpeddi1239
2 жыл бұрын
@@VibhorChandel You are awesome, please do it
@kateykaplan325
Жыл бұрын
Great content Vibhor! Am I mistaken to assume that your 'T-Split' technique splits stories by Scenarios (breath) and Workflow requirements (depth)? Cheers!
@ashishsachdeva8092
3 жыл бұрын
Hey Vibhor, Very well explained 👌
@K-Killerzz
2 жыл бұрын
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?
@adeelahmed8403
11 ай бұрын
what are story points and how we determine the complexity using story points?
Пікірлер: 163