Re:Tasking developers with creating detailed estimates is a ...
by codingdave on Friday November 19, 2021 @08:16AM
(#29276804)
Back in the first dotcom boom, we started tracking our rough swags that a dev would throw out on gut instinct vs. the detailed estimates we put together for actual customer projects. We founds the swag were more accurate, exactly for the reasons you stated -- we would over and under estimate details, but they balanced out and the scope of the overall project was correct. We then got into talks with other dev shops, with more experience than our young group... and they had the same result. Young or old, experienced or not, a rough swipe at the scale of a project is usually accurate enough to know what it will take.
I've seen the same thing play out in Agile processes - we are asked for story points, and while many are accurate, some are way bigger than we thought, some smaller. But the overall time to complete a project tends to fall right about where the devs thought it would before the pointing exercises.
All the estimation in the world will still put the same answers into the hands of your project managers - "Pick a date, or pick your scope. Not both."
I've seen the same thing play out in Agile processes - we are asked for story points, and while many are accurate, some are way bigger than we thought, some smaller. But the overall time to complete a project tends to fall right about where the devs thought it would before the pointing exercises.
All the estimation in the world will still put the same answers into the hands of your project managers - "Pick a date, or pick your scope. Not both."