it is ridiculous that we consultants are so miserable about time estimate. i’ve never been on on a project that’s met it’s time estimate. most have exceeded the time line miserably. a very few have have made it within what i would consider a “normal over- extension”. when that does happen it’s normally been because my consulting group has to deal with a way out of control database or some sort of system outage beyond what the client company would ever admit or even know about.

data management has been the wild buffalo. just as my group is implementing some new functionality in Java on a client’s web site, the data people inform us that “there’s a new installation of Oracle going in on the weekend” – which shuts us down for 3 days through the following Wednesday.

another buffalo is the “change requirements by appearance” approach of so many on the business side of management. here’s what i mean:

originally, the requirements on a project demanded that all users enter their user name, email and password; all of a sudden management says, “all we need are the user name and password. trash the email as a requirement.”;
where do we put the email;
reply: “on the user’s info page”;
there never was a user’s info page in the requirements;
the job continues for 2 more weeks as management decides what to put on the user info page and where to store it;

if i feel cynical that week, i could sit back and wait for the more changes to come. but since i simply cannot be the wisest monkey in the jungle, i figure i better befriend somebody in management to help figure out what’s going on and become part of the decision making process. i then help management come up with an ad-hoc process that solves this problem, management feels good about itself, and i complete the project with a happy client.

thanks for the article. “the rule of pi” is a good one and pretty much matches the real time spent on the projects i’ve been on.

My take on this from my time in IT is that deadlines were fuzzy because they were allowed to be. I met my deadlines because I always assumed I had to but other managers were often allowed to routinely miss deadlines with little consequence.

I once had an IT software manager tell me he had the best job in the company. He and his team could spend six months at a time writing requirements with the client for their next project. Then, before any real volume of code was written, the requirements were changed by the client or the project dropped entirely and they could begin again. He told me he never had to actually deliver a working application.

He did this for the better part of 5 years…

The key is working with a team who is not afraid to say what is happening and have weekly bull sessions. Market windows are key factors and missing them puts you in a world of hurt.

In the early days before I figured this out I had a formula: multiply by 2 and take the next unit of measurement. So a 2 week project = 4 months. Pretty cynical.

I’ve been burning the midnight oil, the candle at both ends and my eyes out trying to meet self-imposed deadlines to produce a set of market documentation for a client who would in fact have been perfectly ok with a longer lead time.

Why the self-delusion? Partly, it’s misguidedly aspirational (I will be super-efficient on this project as I never was before); partly it’s wilfully ignoring the fact that thinking about something before you do it is part of the process and takes time; and for the most part it’s that I hope I’ll work faster if I have a looming deadline.

Great article.

How long would that take? Well, that needs a breakdown of What would that take? Some immediate organization, some thoughts on what needs researching, some thoughts on where the research would lead, some idea of what assets will be available to start, and what assets will be required post-research. Some idea of the historical precedent is needed – will the corporate desire to get it ‘right’, to some high standard prevent a target from being reached that might be ‘good enough’ for others? How much energy is available to get any newly found requirements the permissions required to follow-up or utilize?

Add a percentage for false leads. Add a percentage for tail chasing. Add a percentage for administration. Add a percentage for late coming bright ideas.

Goodness. My response is getting out of hand.

I had a good experience talking to the chief engineer of a project on day, asking what the project would take. I got a general outline and the usual ‘a couple of days’ and ‘a few lines of code’ answers to the time question. The next day I went back and asked the ‘what does it take’ question about one line of the general outline. Got several more particulars. Did the same thing in short bursts for daze…days. Finally, a usable answer was available. And still, all the vagaries of the research and development unknowns manifested themselves.

Try that with an artist who has to develop a piece of art. R&D ain’t so obvious a need, but it is there.

Peer pressure variants (If I don’t do it, the responsibility lands on my co-workers, or Gee, I’ll look like a fool if I hand in something substandard), money, glory, fear, deadlines that can’t move (the convention starts on this date and the product must be shown, working and ready to buy online), deadlines that can shift (the convention starts on this date and the product must be shown, and the main parts need to be working.)

A book or two, perhaps a philosophy.