Mastering Agile Estimation: How to Perfect Story Points Estimation

There is different ways when talking about estimating, we either use relative estimation or Absolute estimation.

Relative complexity is easier to judge than absolute one. if we compare two dogs, it is easier to say which dog is heavier than the other that trying to guess how many pounds does each weigh.

Relative estimation means that we judge how big or complex a task is with respect to other tasks, and the unit of complexity that can be used in this kind of estimation is the story point. A story point is a number that tells the team about the effort required to implementing a given user story.

#agile #businessagility #agility

[OeLean]

📚 GET OUR FREE AGILE BOOKLET WORTH 39$

[twinklebedi]

All your videos on agile are awesome. I had been struggling to understand agile, watched a few videos and read a few blogs, but nothing was as crisp and efficient as your videos. Finally I have a good understanding of how this works. Thanks a ton!!

[TheConfidenceFrequency]

This is such a great example. Your way of explaining things really resonates with me. Thank you!

[boerieza]

I love the video. My only objection is that when we start using a reference story, the video explains that the team only looks at the Effort aspect of the stories rather than the complexity or uncertainty (as described earlier in the video). We've encountered many situations where effort is usually less than the reference story. Still, complexity or uncertainty is way higher...so my comment would be that when sizing against a reference story, all three (3) aspects need to be taken into account, not just effort.

[kevindurham]

Great explanation, but in the end it's still manpower that management cares about, not effort/complexity. The VP of IT cannot say "the feature is delayed by 13 story points" management wants to know about $ = hours.

[funmijeje]

Thank you so much for this short and clear explanation of estimating user stories using story points.

[AbdulWahid-ycpt]

My sincere thanks to you for this professional explanation.

[leespain]

This was a very understandable and succinct explanation. TY.

[SuperAbhishek]

You are awesome, explained so beautifully, God bless you. 😀

[deandaniel]

Very clean explanation, I'm glad that I understood concept well, but concentrate on slang... Some of the world's unble to understand... Just use basic pronunciation... Keep it up... Guys

[Sargam_Cafe]

please make a video on -" how will you estimate a story if you are very much uncertain about a story what it does and how complex it will be in future?"

[jaidevsharma]

Simply and beautifully explained. Thank you.

[suhailsultanmirani]

Your all videos are really interesting

[ColoxixP]

Very concise and useful! Thank you so much!

[noamsonnenberg]

A great video! Clear and easy to understand

[Lateralusx]

Such a great video. Thank you for helping me understand how this works.

[peshutanpavri]

So valuable, I love your videos, very good, detailed yet simple explanation. Only question is, if product owner asks when can a certain task/user story be ready ? How do we use estimation to respond to them?

[dikshamasurkar]

How to handle such situation or scenario where team members are consistently estimating user stories not correctly. Let's take an example there are 1 user story which are simple can be done in 2-5 hrs but still team members are estimating it for say 2 days or so by saying buffer time in that we have experience members as well. How to approach as a SM also how to handle PO and other stakeholders in such case if it is consistently happening for few sprints.

[deronthornton]

4:10 took me out el oh el....great video!

[khaoulagammoudi]

Thank you so much ! It was very helpful to me :)