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.
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 :)
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 🙏
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.
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! 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....
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 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.
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 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?
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.
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 .
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.
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).
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 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.
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!
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?
Good content, I wish you slow down your speech so I can understand specially for beginner learner to this field . I tried to play back slower but it came out too slow.
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.
Probably the best video I've seen on the topic of splitting user stories. Well done.
All I can say is this video convinced me to Subscribe.
Each video I see ,I get to understand different dimensions of agile. Cannot thank you enough.. Accepted you as my agile coach..
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.
Had not heard of the acronym WAHZUR. Thank you for introducing it as a way to break up or write stories
im a student and while doing a project for Software Engineering i came across this video and it helps alot :D
Great video, one of the best visual video ever seen. Thanks for the great job
this is informative, although you have a slightly different approach than others, it does make sense what you are talking about. Thumbs up.
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 :)
This video is amazing! So much knowledge in such an easy explanation and the examples are very helpful
I just came across your videos and I am glued. Thank you for the content
Hi Vibhor , Thats a wonderful video and best part is the Practical Examples and not the Concept . Thank you and Well done
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 🙏
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.
Really a valuable and informative and interesting video. Thanks for sharing such good content.
One of the best explanation for refinement in agile space. Thanks vibhor
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.
I love to watch and learn from your videos. This one is amazing
your explaination made the whole user story funda like a cake walk...casual but impactful explaination. Thanks Vibhor !
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
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....
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
Awesome, precise and crisp
Thank you so much, this video clear so many doubts
Thank you so much for such deep knowledge sharing. a big thx
Thank you Mariem
Thank you from Thailand
All your videos are great! I have been binge watching your videos! Thank you for creating great content thats easy to understand!!
Good man with confidence. Thank you for the video! :)
Thank you for helping and sharing this video
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
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.
Excellent explanations and well made videos Vibhor .
Really excellent summary of the activity...
I love your videos Vibhor!! Very informative. Please keep them coming! 👏🏽👏🏽
Thank you Tosin
This is a really useful video and I like the analogy of the slice of cake.
Very well done man. Great job. You should charge for these kinda vids.
Thanks a lot Vibhor! it is really simple and easy to understand
Thank you! This is super clear
"JUST BE AGILE" 🙌🙏👌
Thank your for Information it’s too much helpful
You are doing a great job, Vibroh, thank you!
Very nice explanation. Thanks. Learnt a lot.
short and on point vibhor... great video.
Thank you for making it look easy
Great learning and thanks for sharing. Looking forward to more such videos.
Great video. I really like the speed and content of your presentations. The examples are invaluable. Keep up the great work.
Its very helpfull thankyou
great explanation sir !
Excellent content..... very informative
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.
very good explanations , thank you
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?
Simply outstanding
Awesome content, its very helpful. Thank you Vibhor.
Mind Blown!
This is definitely really good content! I would be interested in connecting to learn more tips and trick for Agile.
liked it thank you. any inputs on how to roll up weights to stories with tasks.
Looking forward to the tutorial series on “effective user stories”
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.
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 .
You have nailed it 👍
Crisp and Clear Vibhor 👍
Great Video Vibhor .. thank you !!
Very enlightening!
superb
Ur agile Guru sir, thank you for simplifying and helping people like me. Do u also coach one on one??
Great work sir
Excellent awesome!!👍👍👍👍👍👍👍
Very insightful. Can I please get more help on splitting user stories and acceptance criteria.
💯superb video !
Great 👍
Awesome video, the content was really good.
Thank you Raghu
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.
Very good synopsis!
Excellent!!!
very clear!! thanks
Valuable information
Excellent!
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).
Great stuff as always 👍
Hey Vibhor, Very well explained 👌
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?
Is that printed text editor at 10:17 🤣?
Good videos by the way, thank you.
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
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.
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.
Hi. Great video. Friendly heads up, you skipped the V in INVEST while stating what each letter means.
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?
Now I understand why the markets are in recession...
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.
fantastic
Great video👍
Wonderful content.
Good content, I wish you slow down your speech so I can understand specially for beginner learner to this field . I tried to play back slower but it came out too slow.
what are story points and how we determine the complexity using story points?
Do we prioritize epic or user story ?? And how we prioritize user story for story map??
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.
Certainly t split technique is best
Thank you.
Please make a high level video on, "How to build a product from scratch?"