I did some Udemy courses and online researches, but haven't found this level of clarification of this technique. Thank you Sir!
@rabialhassan6044 Жыл бұрын
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 🎉🎉🎉🎉
@gmvicky48578 ай бұрын
Very good explanation. your Clarity of teaching is immense!!!!.
@willydoit4u2c Жыл бұрын
Fibonacci... I'm absolutely blown away! 👍👍👍👍👍👍👍👍👍
@sarahafreenmalik26798 ай бұрын
This was incredible I finally understand! Thank you so much! I found Agile estimation boring, you've made it interesting and fun!
@sumitmhaiskar722 Жыл бұрын
Sir, you're god thanks for explaining agile estimation.
@amrutkulkarni47682 жыл бұрын
What a good explanation sir. I really like it. Thanks for sharing.
@sprintwithcarlos6 жыл бұрын
Very well explained, once your have build your first reference story, everything is easier, thanks!!
@pramodts20263 жыл бұрын
You have explained it very well, good job Ajith
@vbond00073 жыл бұрын
Excellent explanation. Very clear and crisp, Thanks 👍
@jumokeadekunle952 Жыл бұрын
WOW! Thank you so much for this.
@007Katoch4 жыл бұрын
Wonderful explanation short and precise
@anuranjansrivastav98642 жыл бұрын
Explained in great way.. thank you
@kiran13april2 жыл бұрын
Very well explained , thanks for sharing
@tafri9614 жыл бұрын
very precise effort estimation video. thank you Ajeet.
@willydoit4u2c Жыл бұрын
Thank you sir. You are brilliant
@lavanyaveeravarapu91563 жыл бұрын
Awesome , very well explained
@santhoshraghav40386 жыл бұрын
thank you for clear and concise explanation of story point estimation with references.
@AbhishekGupta-sz2li4 жыл бұрын
Another excellent video.
@willydoit4u2c Жыл бұрын
One more thanks, thank you thank you!
@kiranpanda81614 жыл бұрын
Perfect Example
@balajikoc14294 жыл бұрын
Excellent explanation
@LifeWithKrishuu4 жыл бұрын
I really liked it ..very well explained 👍Clarified in a better way👍👍👍
@sumit-oj8ec4 жыл бұрын
yes its good and in ur team u can choose ur 1 sp =8 hrs or 10 hrs based on team to team
@KiranVarri2 жыл бұрын
Well explained... Tyty👏👏👏🙏
@raj609214 жыл бұрын
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
@harmanmaan8706 жыл бұрын
Very Good explanation
@moosaramtota5 жыл бұрын
Very nicely explained, thank you
@saxenarachit5 жыл бұрын
Nice videos... cleared the base concepts... I liked your start 'Hi there, this is Ajit here' :)
@Standoutbrains_5 жыл бұрын
Thanks for the feedback. This is Ajeet here :)
@binduv31014 жыл бұрын
This is awesome
@ramakrishnasvsna78645 жыл бұрын
Well Presentation sir , Thank you
@sriiyer64843 ай бұрын
Thank you 🙏🏽
@arpitadharma19105 жыл бұрын
awesome, great job
@tanushastrology19733 жыл бұрын
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?
@vaibhavsharma31276 жыл бұрын
Good Explanation... Cheers
@dinnsh3 жыл бұрын
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
@Standoutbrains_2 жыл бұрын
Please book a session with me we can discuss. Here is the link calendly.com/ajeetsingh0401/coachingwithajeet
@yatindesai53096 жыл бұрын
excellent
@lemaitrejean46394 жыл бұрын
For beginner, best recommendation is to use a matrix : time consuming and complexity
@sanketshintre84366 жыл бұрын
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
@matthoffman6962 Жыл бұрын
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.
@jayantobhattacharya71273 жыл бұрын
Need real time example that How a scrum master help the product manager by discovering new techniques in product backlog management?
@ganeshk57213 жыл бұрын
How a UI developer know about db efforts , and finally arrive at (comment) about the story points
@Standoutbrains_2 жыл бұрын
Please book a session with me we can discuss. Here is the link calendly.com/ajeetsingh0401/coachingwithajeet
@NikhilYadav-nm8bu5 жыл бұрын
Ajeet, if you know thw amount of work, size of the development & complexity before estimating then it is traditional way of estimating
@Standoutbrains_5 жыл бұрын
Just because you estimate in Agile, doesn't mean you can't consider these factors. Idea is to stay predictable whatever way possible. At the end it would get revised based on emerging realities. Thanks for your comments 🙂
@shishirsoni89965 жыл бұрын
Excellent video...could you please share some videos of interview questions on Scrum.