Agile Estimation Reference Story Technique with Examples
Connect for a session at - ajeetsinghthecoach@gmail.com
#coachingwithajeet #scrummaster #agile #agilecoach #interview #scrummasterinterview #agilecoachinterview #interview
"Landing on story point mode of estimation is not always easy, especially for those who have been estimating the software's in hours and now as part of Agile implementation, been asked to switch to the relative estimation. This video talks about a technique that can help people easily transition from hourly mind-set to the story point estimation mind-set, reaping the benefits as early as in the agile delivery."
Пікірлер: 64
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 🎉🎉🎉🎉
This was incredible I finally understand! Thank you so much! I found Agile estimation boring, you've made it interesting and fun!
Very good explanation. your Clarity of teaching is immense!!!!.
thank you for clear and concise explanation of story point estimation with references.
Very well explained, once your have build your first reference story, everything is easier, thanks!!
Fibonacci... I'm absolutely blown away! 👍👍👍👍👍👍👍👍👍
Excellent explanation. Very clear and crisp, Thanks 👍
WOW! Thank you so much for this.
Sir, you're god thanks for explaining agile estimation.
Explained in great way.. thank you
Very nicely explained, thank you
What a good explanation sir. I really like it. Thanks for sharing.
awesome, great job
very precise effort estimation video. thank you Ajeet.
Wonderful explanation short and precise
Well Presentation sir , Thank you
Very well explained , thanks for sharing
Another excellent video.
Thank you sir. You are brilliant
You have explained it very well, good job Ajith
Good Explanation... Cheers
Awesome , very well explained
Excellent explanation
Very Good explanation
One more thanks, thank you thank you!
This is awesome
excellent
Well explained... Tyty👏👏👏🙏
Perfect Example
I really liked it ..very well explained 👍Clarified in a better way👍👍👍
Thank you 🙏🏽
yes its good and in ur team u can choose ur 1 sp =8 hrs or 10 hrs based on team to team
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?
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 :)
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 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
For beginner, best recommendation is to use a matrix : time consuming and complexity
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
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 🙂
Need real time example that How a scrum master help the product manager by discovering new techniques in product backlog management?
Excellent video...could you please share some videos of interview questions on Scrum.
@pavasmalviya3115
5 жыл бұрын
itsasixdude.blogspot.com/2018/12/agile-scrum-scrum-master-interview.html
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
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.
If you have story point of 8 ,how many hours required to complete the story.
@poonamk1372
Жыл бұрын
need answer for this
Please also give presentation on effort estimation.
@Standoutbrains_
2 жыл бұрын
Please book a session with me we can discuss. Here is the link calendly.com/ajeetsingh0401/coachingwithajeet
Are there no critical path and precursor tasks logics associated here?
@Standoutbrains_
3 жыл бұрын
This is agile way of estimating
@Standoutbrains_
2 жыл бұрын
Please book a session with me we can discuss. Here is the link calendly.com/ajeetsingh0401/coachingwithajeet
How I can get in contact with you master
@Standoutbrains_
2 жыл бұрын
Please book a session
@Standoutbrains_
2 жыл бұрын
calendly.com/ajeetsingh0401
How come dba or tester etc can give end to end estimation?
@Standoutbrains_
11 ай бұрын
Plz book a session