Re: Dev Project Estimates
Thanks, I checked out the full article over on Dr. Dobb's, that was very in-depth! Of course, it has every right to be so - Project Estimates are something we've all struggled with since the dawn of time, and the modern software development landscape does not make things any easier! To that end, I like your approach here - not that this methodology is a one-shot bandaid that will fix your problems (because there isn't one), but that, over time, it will lead to a generally better software development environment, and a better way of understanding your own estimates internally. After all, isn't that what's most important? an estimate can only be 'accurate' if everyone on the team agrees on it and what it means.
The other benefit of this methodology is that stretches and scales regardless of the product at hand. You can move to a completely different kind of project, and while it will require plenty of adjustments (IE the relative scale of this 'work story' items), this basic template will still function. On the other hand, the whole thing hinges on your team members being on board, and you can't always wring blood from a stone. If they don't like the model, or if they don't compensate for the 'cost of doing business', etc., you won't get accurate estimates, whether it's time or some other measurement. There's really no way around that.