I did some Udemy courses and online researches, but haven't found this level of clarification of this technique. Thank you Sir!
@govindckumar22 күн бұрын
Very much informative thanks for the help
@gmvicky4857 Жыл бұрын
Very good explanation. your Clarity of teaching is immense!!!!.
@sarahafreenmalik2679 Жыл бұрын
This was incredible I finally understand! Thank you so much! I found Agile estimation boring, you've made it interesting and fun!
@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 🎉🎉🎉🎉
@willydoit4u2c2 жыл бұрын
Fibonacci... I'm absolutely blown away! 👍👍👍👍👍👍👍👍👍
@sumitmhaiskar7222 жыл бұрын
Sir, you're god thanks for explaining agile estimation.
@jumokeadekunle9522 жыл бұрын
WOW! Thank you so much for this.
@amrutkulkarni47682 жыл бұрын
What a good explanation sir. I really like it. Thanks for sharing.
@pramodts20263 жыл бұрын
You have explained it very well, good job Ajith
@SolidiniАй бұрын
Great video with a lot of detail on the technique. Since we're now all working from home a lot, which requires a lot of async work. What do you think of tools that help the team do async estimations (or async poker)?
@kiran13april3 жыл бұрын
Very well explained , thanks for sharing
@anuranjansrivastav98642 жыл бұрын
Explained in great way.. thank you
@willydoit4u2c2 жыл бұрын
Thank you sir. You are brilliant
@007Katoch4 жыл бұрын
Wonderful explanation short and precise
@sprintwithcarlos6 жыл бұрын
Very well explained, once your have build your first reference story, everything is easier, thanks!!
@tafri9615 жыл бұрын
very precise effort estimation video. thank you Ajeet.
@LifeWithKrishuu4 жыл бұрын
I really liked it ..very well explained 👍Clarified in a better way👍👍👍
@lavanyaveeravarapu91563 жыл бұрын
Awesome , very well explained
@vbond00073 жыл бұрын
Excellent explanation. Very clear and crisp, Thanks 👍
@willydoit4u2c2 жыл бұрын
One more thanks, thank you thank you!
@santhoshraghav40386 жыл бұрын
thank you for clear and concise explanation of story point estimation with references.
@AbhishekGupta-sz2li4 жыл бұрын
Another excellent video.
@balajikoc14295 жыл бұрын
Excellent explanation
@kiranpanda81614 жыл бұрын
Perfect Example
@KiranVarri2 жыл бұрын
Well explained... Tyty👏👏👏🙏
@moosaramtota5 жыл бұрын
Very nicely explained, thank you
@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
@harmanmaan8706 жыл бұрын
Very Good explanation
@ramakrishnasvsna78645 жыл бұрын
Well Presentation sir , Thank you
@binduv31014 жыл бұрын
This is awesome
@sriiyer64847 ай бұрын
Thank you 🙏🏽
@Wolfpack0076 жыл бұрын
awesome, great job
@vaibhavsharma31276 жыл бұрын
Good Explanation... Cheers
@saxenarachit6 жыл бұрын
Nice videos... cleared the base concepts... I liked your start 'Hi there, this is Ajit here' :)
@Standoutbrains6 жыл бұрын
Thanks for the feedback. This is Ajeet here :)
@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
@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?
@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
@Standoutbrains3 жыл бұрын
Please book a session with me we can discuss. Here is the link calendly.com/ajeetsingh0401/coachingwithajeet
@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
@yatindesai53096 жыл бұрын
excellent
@amitb1493 жыл бұрын
Are there no critical path and precursor tasks logics associated here?
@Standoutbrains3 жыл бұрын
This is agile way of estimating
@Standoutbrains3 жыл бұрын
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
@Standoutbrains5 жыл бұрын
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 🙂
@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.
@mahapol88125 жыл бұрын
If you have story point of 8 ,how many hours required to complete the story.
@poonamk1372 Жыл бұрын
need answer for this
@lemaitrejean46394 жыл бұрын
For beginner, best recommendation is to use a matrix : time consuming and complexity
@caomengde164519 күн бұрын
My question is- why bother creating a reference use story estimate- if the estimate relies upon concensus and judgement? i ask this because i saw lots of scrum masters doing user story estimate reference yet at the conclusion of the sprint the reference is not even considered- i mean it became just a waste of time and effort!
@shishirsoni89966 жыл бұрын
Excellent video...could you please share some videos of interview questions on Scrum.