3 ms·
To accurately estimate means developers and product management have collectively discussed the requirements to a level everyone understands clearly. Without th
by sanguy 5y ago
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.
- gortok 5y agoIt’s just “a spike” or “spike”.
- bigwavedave 5y ago> 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.
- sanguy 5y agoYes, thanks! You'd make a great developer with the perception of the error cause before confirmation ;)
- sanguy 5y agoYea sorry, autocorrect strikes.
- rorykoehler 5y agoFor most saas out there, once all the requirements are that well understood the product is already 70% built.
- sanguy 5y agoThis is very true. A great product manager is as priceless as a great developer.