It's upsetting when the rug is yanked from under your feet.
Situation:
I'm sitting in a conference room holding a technical discussion with my development team on the best manner to handle a systems interface. We've pretty much figured out the best solution to the problem and were working through some implementation details so that we could quickly beat the problem.
And then my boss comes into the room...
"Can you explain how the site is architected?" he asks. I begin to explain the general structure to the app, keeping it high level so as not to get bogged down.
"We have a problem. The TC's have reversed their decision about J2EE applications on the shared servers. They won't let it go into production on the shared environment."
Needless to say, I am floored.
"Any reason why?" I asked.
"Something to do with how the web connector won't work for the NAS 2.1 apps if you have J2EE apps in the same environment."
bullshit I'm thinking.
So now I'm sitting here, thinking of ways to mitigate this big, flashing, warning sign that I'm putting into my status report. It's not looking pretty folks. Any time management comes into the room and says "It's got to be stellar, so take all the time that you need: your schedule has been blown out of the water..." to a project team that is operating ahead of schedule it's not going to be pretty.
