Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

To accurately estimate means developers and product management have collectively discussed the requirements to a level everyone understands clearly. Without this an estimate is as accurate as a weather report for 90 days out.

A good estimate may also require "spiked" to test concepts to get to a reasonable estimate.

I'm currently in a project that is terrible as the development team provides estimates without even reviewing the requirements and now "18 months late" with many pissed off stakeholders. It is a caustic situation. People are quitting the company due to the politics, frustration, and pressure due to this.



For most saas out there, once all the requirements are that well understood the product is already 70% built.


This is very true.

A great product manager is as priceless as a great developer.


It’s just “a spike” or “spike”.


> It’s just “a spike” or “spike”.

I imagine the OP meant "spikes" and either accidentally hit the 'd' instead of the 's' or simply fell victim to autocorrupt.


Yes, thanks!

You'd make a great developer with the perception of the error cause before confirmation ;)


Yea sorry, autocorrect strikes.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: