3 ms·
One of the things I sometimes say to our clients at my workplace is that estimation can be done two ways. The traditional way is summative. Take all the things
by jacques_chester 12y ago
One of the things I sometimes say to our clients at my workplace is that estimation can be done two ways. The traditional way is summative. Take all the things you want to do, estimate them (which is where McConnell's book really shines), then produce a range that expresses your likely outcomes.
The other way is emergently. Build a pile of things you want to do, put them in rough order of value, then estimate a few things at a time. Then start working. Only after a few weeks will you be able to begin to predict outcomes.
This is old news. I'm talking about velocity. Which is actually the perfect word, because summative estimations are about a total distance travelled; velocity is about the speed and direction you're currently moving in. Velocity is the differential of the project's outcomes.
Velocity is a more powerful metric because it includes its own mechanism for updating estimates. A classic "estimate smell" is that the first estimate made is the last estimate ever made. The closely related smell is "estimates that fit the plan", aka "estimation by fiat".
Velocity, however, emerges from observation. No additional action is required to update summative estimates. And what comes for free is typically, in software methodology, all that gets done.
Another way in which moving to velocity as your estimating technique is that you change what is fixed and what is fluid in discussions with clients. Traditional project management takes the work breakdown as a fixed outcome and then looks to optimise around that. Time, schedule and quality are then the variables. Velocity allows you to vary scope and work as well. You can then hold quality, time and schedule constant instead.
It's hard to convey how big of a deal this is in practice. It seems like a minor alteration. But taking seriously that the speed of light in a vacuum is fixed (per Maxwell's equations) means that spacetime varies. Which makes ... a big difference to physics.
I have seen this change in thinking bring high-risk projects to a successful conclusion under tight deadlines, with high friction, with high technical demands, in short timeframes. We had the data to show where the project was going, and that allowed us to focus on ensuring we were delivering in order of value. It also allowed us to discuss with the client what was possible and what was not possible.
Under traditional schemes we'd have had a fixed pile of features and the project would've been a "failure". Yet it did everything that was needed on a particular day, with very generous margins of safety.