I did some Udemy courses and online researches, but haven't found this level of clarification of this technique. Thank you Sir!

I’m glad I stumbled on your video before I took the PSM1 exams today.I passed on the first try.. Thank you for all the resources you provided everyone one of it was useful and helpful 🎉🎉🎉🎉

Very good explanation. your Clarity of teaching is immense!!!!.

Fibonacci... I'm absolutely blown away! 👍👍👍👍👍👍👍👍👍

This was incredible I finally understand! Thank you so much! I found Agile estimation boring, you've made it interesting and fun!

Sir, you're god thanks for explaining agile estimation.

What a good explanation sir. I really like it. Thanks for sharing.

Very well explained, once your have build your first reference story, everything is easier, thanks!!

You have explained it very well, good job Ajith

Excellent explanation. Very clear and crisp, Thanks 👍

WOW! Thank you so much for this.

Wonderful explanation short and precise

Explained in great way.. thank you

Very well explained , thanks for sharing

very precise effort estimation video. thank you Ajeet.

Thank you sir. You are brilliant

Awesome , very well explained

thank you for clear and concise explanation of story point estimation with references.

Another excellent video.

One more thanks, thank you thank you!

Perfect Example

Excellent explanation

I really liked it ..very well explained 👍Clarified in a better way👍👍👍

yes its good and in ur team u can choose ur 1 sp =8 hrs or 10 hrs based on team to team

Well explained... Tyty👏👏👏🙏

Login can be complex than entry form User story, if we are going to use OIDC OAuth flow for login, in this case reference technique will fail. As per my understanding User story estimation should be relative as well as Actual complexity

Very Good explanation

Very nicely explained, thank you

Nice videos... cleared the base concepts... I liked your start 'Hi there, this is Ajit here' :)

This is awesome

Well Presentation sir , Thank you

Thank you 🙏🏽

awesome, great job

Clear and crisp explanation with good clarity. Sir after we get story points, to map it to days or hours do we use the Hours-Story point table you had shown in the video?

Good Explanation... Cheers

Thanks for the video. Usually, this story point estimation happens in which scrum / agile ceremony ? Sprint planning or PB grooming or in both ? Also, who is wholly responsible for the story points allocation ? The scrum team or Product owner ? - It would be great if you clarify this

excellent

For beginner, best recommendation is to use a matrix : time consuming and complexity

Very well... sir i would like to see a user story and acc criteria written for an actaul functionality... i have been working in waterfall... want to switch to agile as a ba

While I think the Fibonacci scale is probably a better use of “give me an estimated hour count” but what’s the difference between a 3,5 or 1,2. There’s practically no difference. So at that point you’re just making up the estimation.

Need real time example that How a scrum master help the product manager by discovering new techniques in product backlog management?

How a UI developer know about db efforts , and finally arrive at (comment) about the story points

Ajeet, if you know thw amount of work, size of the development & complexity before estimating then it is traditional way of estimating

Excellent video...could you please share some videos of interview questions on Scrum.

If you have story point of 8 ,how many hours required to complete the story.

Please also give presentation on effort estimation.

Are there no critical path and precursor tasks logics associated here?

How I can get in contact with you master

How come dba or tester etc can give end to end estimation?