Quote:
Mcoyote wrote:
I guess I'm sympathetic because I work in software. The business has certain goals that translate into dates and units, but the engineers often won't know what they'll encounter on the way there -- some things just can't be predicted when you are dealing with this much code.
|
I agree with Mcoyote here as I work in the software industry too.
However, I also agree with his later statement of:
Quote:
That being the case, engineering management would be well served to be pessimistic in their timelines...
|
I worked with a software company about five years ago that sold document imaging systems. They basically missed the boat of having a totally web-based system so they were cracking the whip hard on the development staff to convert the current client-server app. into a web-based one. THEY DROPPED ALL THEIR P.R. MATERIALL TOO EARLY AS WELL...
This caused their existing clients to stop ordering new licenses as they feared an imminent upgrade/conversion and scared their prospective clients into waiting to give them any money because they did not want to be on the "Bleeding Edge" of a new and untested technology.
For Access it is a little different in that a Virus C is still a bad-ass synth and some people might not be shy in buying it even I they know the TI is coming out. It is still bad business, but in al honestly it is a difficult game to win.
No company will ever have their product designed, tested, manufactured and on a perfectly predictable delivery schedule; no matter what business they are in. In general though it is better practice to UNDER PROMISE and OVER DELIVER.
I also agree with 3o3:
Quote:
3o3 wrote:
That's right - don't stand in the way between my beer and my other beer. damn it.
|
This is a fundamental law of man...
...and apparently apes as well!
-AlexHall74