views:

205

answers:

9

I'm needing a term or established term to represent a phenomenon our company currently calls a 'Black Hole': a project that takes magnitudes longer than estimated, yet we're already sucked in and HAVE to see it through to completion.

EDIT: Hoping that the best term will be voted up.

+1  A: 

"Scope creep" is the phrase I've used.

Dean J
I'd expect "scope creep" to apply to projects whose scope is expanded, rather than just woefully under-estimated.
Vatine
+4  A: 

Screwed.

Matthew Jones
+13  A: 

I believe the term you are looking for is Death March, though I suppose it doesn't really apply if the project is ultimately successful.

tvanfosson
Definitely Death March - http://en.wikipedia.org/wiki/Death_march_(software_development)
ssakl
Sounds like this is a contract type of project, which you're legally bound to finish, thus it can't fail, but your company just losses a bunch of money on it. I've often heard these referred to as "Money Pit" projects.
smoore
It still applies to succesful projects. The term is about the jouney, not the destination.
T.E.D.
It depends on likelihood of failure and what your company's definition of failure is. Many companies don't consider going way over budget to be a failure, as long as the project satisfies the customer and the company doesn't go bankrupt.
smoore
+3  A: 

I would say "Underscoped".

I am involved with an underscoped project at the moment.

Dylan Berry
A: 

Since hours are often associated with cost, perhaps the term you seek is Cost Overrun?

I also like the concept of Optimism Bias as the reason for under estimating.

Mayo
A: 

I remember 'logic bombs' applied to compressed files. Mainly, create a (back then, several gigs) file containing only one symbol repeated over and over. Zip the file (will become tiny). Send to user -> balloon effect.

Perhaps balloon project? Murphy's Project?

lorenzog
+1  A: 

I once interviewed for a position on what had to be the ultimate Death March project. I was at Lockheed Martin at the time. Here's what I discovered at the interview:

  • The project was almost entirely staffed by engineers pulled off of the layoff list. Pretty much the dregs of the company.
  • They were using castoff equipment from the rest of the company for their software development.
  • 15 hours a week of overtime was mandatory, and would be for the foreseeable future.
  • They didn't even have cubicles. Everyone worked in one great big open bullpen with wires strung everywhere.
  • They had attempted to deliver this project once before, but the customer rejected it and made them try again.
  • They were so far over budget and so late that nobody was even bothering to track it anymore.
  • They wanted to cancel the project, but their customer was the government of Egypt and they were threatening to stop a large order of F-15s until this project was delivered. (The project had nothing whatsoever to do with F-15s). So now they were getting pressure to finish from the Chairman of Lockheed Martin on down.
  • Engineers visiting the customer site in Egypt had come down with nasty staph infections. One had to be medevacted out to Europe.

I swear I practically ran from the room.

T.E.D.
A: 

Spike may be useful in trying to get these under control but it isn't quite what you want.

JB King
A: 

"Mind the Gap", read this:

http://blogs.countersoft.com/index.php/2009/11/mind-the-gap

FredFlint