Story Points vs Hours: Which One Is Better and Why? (Agile Estimation Explained)

Here's what we will cover in this video:
- What are estimations?
- Difference between waterfall estimations and agile estimations
- What are story points estimations?
- Can you convert story point to hours?
- How to estimate using agile story points
- What are the pros and cons of estimating in hours and mandays
- What are the pros and cons of estimating in story points
- Estimating in hours vs story points compared, which one is better?
- How to use story points for planning in agile
- How to calculate velocity using story points

What this channel is about:
The #1 place on YouTube for all things Agile.

This channel explores:
- Agile methodology, principles and value
- Agile advanced scrum masters training
- Scrum developer, scrum product owner
- Kanban, Extreme Programming (XP)
- Agile project management and software development
- Agile SAFe
- etc.

I want to hear from you. Please ask your question, provide feedback and give your point of view on the topic in the comment section below. Thanks for your support

[agilecoach]

I make $0.00 on this YouTube Channel. All I ask in return is a little flick on that LIKE button, and maybe SUBSCRIBE to the channel if you enjoyed the video.

Thanks for your support 🙌

[rajeswarikv]

Hello Coach, For hours, we break down to sub tasks and estimate like average of min to max hours . But then if a slow person picks or if dependency or risks occurs, this the time estimated will not be met :) . Also we cant estimate on the waiting time for external or internal dependencies once its identified.. Answering clients, PO, and Management is always a problem in the Agile World..

[jackrhodes]

i think this is your best video yet, insightful

[RahulBorole-hxvf]

If we follow the agile approach then its dont allow to estimate in hours but when we are pulling down user stories from PBI to Sprint Planning, then how many user stories we have to pull?
For eg: Team Capacity : 220 hours for 2 week sprint then how many user stories we can take in the sprint planning?

[bovineox]

I would argue that an estimate is an informed guess at worst. Cone of Uncertainty and all that...

[K-Killerzz]

could you create a video about how to convince stakeholders to estimate the story point instead of hours? Because as I know that many stakeholder always ask How long it will be done?

[gayathrimk]

Hi coach
Could you do a video on what a SM should focus on first 30-90 days to their new/existing scrum team?

[DevTeam-yj]

I prefer to solve this problem by breaking the user story down into deliverables and using a range of hours to estimate each deliverable, a min-max. The reason is because clients push for a timeline. Clients also don't understand project size or story points as a measurement of how long they should expect to wait until their project is complete. If you provide a min-max for each task and them them up then you solve this problem.

[GasserAyad]

Probably man/hour is better suited for estimating fine-grain sub-tasks. But a team may not even need to put an estimate for that. So T-shirts and Story Points remain the most versatile units for estimation.

[benarcher]

Your content is relevant, latest, awesome 🙏👍 keep going sir