Ideal Hours vs. Story Points for Agile Estimates

There is a never ending battle between those who insist on estimating in story points and business people who say "how many man hours will that be?"

I have also never been involved in an Agile project that does any validating of how accurate the prior estimates were. But Ideal Days could easily be validated by the business.

I am considering Ideal Hours. Day are too large, ideal or not.

How about Ideal Fibonacci Hours?

I'd like to hear what things others have tried, but an leaning away from points...

curiouswebsterSoftware EngineerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jessica RigaProducerCommented:
I am a huge advocate for pointing with fibonacci numbers.

Fibonacci Hours is an interesting idea. I could see it being challenging to convert or understand large items (+144), but suppose this would be overcome eventually with practice as your teams get familiar with the system.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
curiouswebsterSoftware EngineerAuthor Commented:
Fibonacci "Ideal" Hours.

I think this would bridge the gap between developers and the business, which needs to always resolve to headcount.

I suppose, a solution to estimate vary large tasks is to break it up into smaller tasks, for example 13 or 20 points being the max.

I even consider making distinct tasks for testing and developing, in some cases. Each of the two tasks would be handled by different developers. I think this would encourage pair programming as needed, and make the tester more objective than developers can sometimes be with their own code.

I read criticisms of Ideal Days versus the abstraction of Story Points. But personally, I have never been on a project that tried to validate the accuracy of the Story Point estimates. While a Fibonacci Ideal Hours method, the comparison would be easy and implicit.

curiouswebsterSoftware EngineerAuthor Commented:
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.