This is the need of the hour since we have of content theortically but not practically...well articulated...appreciation to all the poeple who have contributed!!!
Currently i am facing same issue as in User story 2 where we are having too much uncertainties because client is using open source solution for mocking dependencies and client now want's to extend the product to add some features not supported currently and there is lot much uncertainty to implement that. Now i got to know how to handle this. We can consider it as spike and come up with something. Kudos team! thanks for this session
Great help for a new Scrum Masters, keep doing it. And, there is a question, when this estimation is done, Sprint Planning meeting or Backlog grooming meeting
Thanks for the great session. But as a scrum master, how to check whether my team member is underestimating or overestimating? How to cross verify that the developer is estimating properly?
estimation is just forecast, at the end of sprint team will know if they over/underestimate and thats ok, in retro, team can discuss about the reasons and way forward
If I could ask another question: When using the fist-of-five, usually, there is a proposition that the participants are indicating their level of agreement with; I don't remember hearing that proposition. Is my understanding of how it works incorrect?
Yes, True, its there, may be you missed . watch till end where we discussed about anti-patterns, in the beginning we are doing few things wrong on purpose (anti-pattern)
Great initiative but I have a question. You seemingly having a discussion on the story with various stakeholders (eg, developers, testers, etc). You seemingly used Fist-of-Five to get some feedbacks in order to determine the story points. However, isn't story points decisions are solely the purview of developers?
Hey taffy, thanks for your comment. when we say- developer- it consist of all - front end / back end / tester etc. we don't have any distinction , for us all are Developers. Do let me know if you want to join our whatsapp group, we can have details discussion if required :)
Very thanks for this practical session. Bt i think it could be done shorter, or make separate video for theory and practical. Sometimes people hesitate to open these videos by seeing the long duration.
Thanks for your feedback , but we need to cover the Theory + Practical at one place , so viewer get all info at one place . person can skip/fast forward the Theory part if they are confident enough .
It’s a relative scoring method , exponential in nature. You may use linear ranking 1,2,3,4 etc but it makes it challenging to estimate relative complexity , for example take a user story estimated 6 by one person , and 7&8 by some other people .How can we finalize it faster, with three numbers n close range.Instead with Fibonacci it is either 5 or 8 which can be relatively medium or complex respectively and much easier to determine.
![[ USA 5 Offers] scrum master interview questions and answers ⭐ scrum master interview questions](http://i.ytimg.com/vi/vgLxDlBt61o/mqdefault.jpg)
Scrum as a theory is available everywhere, glimpse of practicality is rare. Keep growing 👏
Thanks for encouraging words 👍
This is the need of the hour since we have of content theortically but not practically...well articulated...appreciation to all the poeple who have contributed!!!
thanks for participation
The Amount of VALUE GAINED in this one video cant even !!!! loved this so much
Many thanks 😊, if possible please do share with your LinkedIn connections or other agile whatsapp groups
Invaluable content for those who need to grasp agile and scrum fundamentals to be cleared
Great you find value, please share with others
Currently i am facing same issue as in User story 2 where we are having too much uncertainties because client is using open source solution for mocking dependencies and client now want's to extend the product to add some features not supported currently and there is lot much uncertainty to implement that. Now i got to know how to handle this. We can consider it as spike and come up with something. Kudos team! thanks for this session
Great you find value 👍
Learnt lot of things with the actual practical session. Thank you Sunand and team!!
great you find value
Thank you whole Team. It was overloaded with knowledge. Love you guys,keep it up.
Special thanks to Sunand and Salvi because your way of explaining things is too good. Stay blessed.
Thanks for your generous feedback 👍
It has been a greatest session i have come across so far in youtube.
Realtime exposure .
Keep doing videos like this.
Really helpful
Many thanks for encouraging words. We have done real time session on sprint planning, sprint review, sprint retrospective. Please watch them as well 👍
The use cases and role play is amazing, lot to learn about dos and don'ts and Anti-patterns etc...
Great you find value 👍
This is great innovative way to help people who are looking for guidance.. thank you for sharing 👍🏻
Glad you like it👍
I really liked this. I mean you don't get this in practical. And the way you All put inputs from all members. Is just incredible..👌👌
Glad you enjoyed it!
Warranty user stories are basically like if we have any bug from onsite with in warranty period after deployment
@CareersTalk, thanks for making this video.
Glad you like it
Detailed demo . Thanks
Glad you liked it!
it brings have real time experience. Thank you so much
You're most welcome
hi this great practical oriented video
Glad it was helpful!
Thanks for the tremendous help.
Glad it helped!
Great help for a new Scrum Masters, keep doing it. And, there is a question, when this estimation is done, Sprint Planning meeting or Backlog grooming meeting
backlog refinement
Superb👏🏼👏🏼👏🏼👏🏼👏🏼👏🏼all doubts cleared
Glad you like it👍
@@CareersTalk Please make a session on bug tracking and reporting on JIRA the bug life cycle part
good one
Thank you! Cheers!
Thanks for the great session. But as a scrum master, how to check whether my team member is underestimating or overestimating? How to cross verify that the developer is estimating properly?
estimation is just forecast, at the end of sprint team will know if they over/underestimate and thats ok, in retro, team can discuss about the reasons and way forward
Excellent
Thank you! Cheers!
If I could ask another question: When using the fist-of-five, usually, there is a proposition that the participants are indicating their level of agreement with; I don't remember hearing that proposition. Is my understanding of how it works incorrect?
Yes, True, its there, may be you missed . watch till end where we discussed about anti-patterns, in the beginning we are doing few things wrong on purpose (anti-pattern)
Great initiative but I have a question. You seemingly having a discussion on the story with various stakeholders (eg, developers, testers, etc). You seemingly used Fist-of-Five to get some feedbacks in order to determine the story points. However, isn't story points decisions are solely the purview of developers?
Hey taffy, thanks for your comment. when we say- developer- it consist of all - front end / back end / tester etc. we don't have any distinction , for us all are Developers. Do let me know if you want to join our whatsapp group, we can have details discussion if required :)
@@CareersTalk Thanks, I now understand.
@@CareersTalk would like to be part of the group. Could you please share the link. Thanks.
Very thanks for this practical session. Bt i think it could be done shorter, or make separate video for theory and practical. Sometimes people hesitate to open these videos by seeing the long duration.
Thanks for your feedback , but we need to cover the Theory + Practical at one place , so viewer get all info at one place . person can skip/fast forward the Theory part if they are confident enough .
Why will use Fibonacci series estimation? Could you please answer my question as I got this question in one of the interview.
will cover in future
It’s a relative scoring method , exponential in nature. You may use linear ranking 1,2,3,4 etc but it makes it challenging to estimate relative complexity , for example take a user story estimated 6 by one person , and 7&8 by some other people .How can we finalize it faster, with three numbers n close range.Instead with Fibonacci it is either 5 or 8 which can be relatively medium or complex respectively and much easier to determine.
Pls share agile estimation excel sheet (a sample)
Drop email to sunandsharrma@gmail.com , along with subscriber 😀 screen shot will send tomorrow
Really great insights but the background noise at times was annoying and distracting.
Thanks for feedback
Can you add me to your WhatsApp group pls. I’m a new scrum master and i need insights
Pl add me to WhatsApp group too