Software estimating is plagued by dysfunction, not the least of which is estimation based on under-reported historical hours from previously completed projects. See posting IT Performance Measurement… Time Bandits for a discussion about this problem.
BUT, other problems are prevalent when launching a project estimating initiative which I call the “Dog Chasing Its Tail” syndrome. It symptomizes dysfunctional project behavior that is established and continues to be reinforced to the detriment of the organization. As a result the pattern repeats and process improvement is seldom realized.
What is the Dog Chasing its Tail Syndrome? It’s a noble goal to increase the predictability and reliability of project estimates – when estimating is based on sound principles. However, estimating is often a misnomer for what should be called “guesstimating” because the data on which estimates are based is sketchy at best.
Here’s the process epitomized in the “Dog Chasing its Tail”:
1. Incomplete (or preliminary) requirements and sketchy quality/performance requirements. While preliminary (no formal requirements or use cases are known), it is customary for management (customer or supplier or both) to demand a project estimate for budget or planning purposes. Labelled initially as a “ball park estimate” (a rough order of magnitude (ROM) guess of whether the effort is going to be bigger than a breadbox or smaller than a football field), the sketchy requirements are used as the basis to get the ROM.
2. The (Guess)timate becomes the project budget and plan. While management initially understands that an estimate is impossible without knowledge of what is to be done, estimators contribute to the reliance on the guesses by providing them with a feigned level of accuracy (e.g., if requirements span a total of two sentences, the resultant estimate may include hours or dollar figures with the ones digit filled in. As a result, too often the (guess)timate becomes the approved upper limit budget or effort allowance. Of course these figures will be proven wrong once the solid requirements are documented and known, but we are now stuck with this project estimate.
3. Changes challenge the status quo budget and schedule. When a change or clarification to requirements emerges (as they always do when human beings are involved), there is often a period of blame where suppliers allege that the item in question is a change (addition) to the original requirements on which the estimate was based, while the customer alleges that it is simply clarifies existing requirements. Of course, neither one can be proven correct because the requirements on which the estimate was based were sketchy, incomplete and poorly documented. Once the dust settles and it becomes clear that the item will impact the project budget and schedule, the change/clarification is deferred to the next phase (“thrown over the fence” as an enhancement to be done in the next release) where it will be poorly documented but we will estimate it anyways, and so the cycle continues.
If you’ve ever had a dog – you know that this is similar to a dog-chasing-its-tail whereby the behavior goes on until either the dog gets tired or gets distracted by other things going on (such as food being served). As smart software engineers we ought to be smarter than dogs! And, given a scope management approach, we can be! Break the cycle off dysfunctional estimation and investigate scope management – you and your customers will be glad to move forward rather than facing the insanity of repeating the same process over and over and expecting different results (along the lines of the Einstein quote!) See http://www.qualityplustech.com for information on scope management training and resources available to break the “Dog Chasing its Tail” syndrome on your projects
Watch for the upcoming post on the hidden dangers in project hours…
To your successful projects!
Carol Dekkers provides realistic, honest, and transparent approaches to software measurement, software estimating, process improvement and scope management. Call her office (727 393 6048) or email her (firstname.lastname@example.org) for a free initial consultation on how to get started to solve your IT project management and development issues.
Contact Carol to keynote your upcoming event – her style translates technical matters into digestible soundbites, with straightforward and honest solutions that work in the real world!
=======Copyright 2010, Carol Dekkers ALL RIGHTS RESERVED =======