My big project at work was scheduled to go into production next Saturday (the 15th). But, of course, several gotchas came up at the 11th hour. So, in our team meeting yesterday I proposed, and everyone accepted, that we delay our launch until the first Saturday in January. I still have a boatload to do (hence the reason for the delay), however, I now feel that I may be able to address most of the issues that have come up before we launch. I'm sure that our user population will still find issues that we haven't found in testing when we finally do launch. However, I couldn't go forward when there were known issues staring us in the face.
One thing that we did agree to that should be interesting: Any known issues that we have when we launch will be documented on an internal Wiki server. So, basically, our response to unresolved issues will be: "Yeah, we know about it. We'll fix it when we can. Get over it." So, as long as we 'advertise' that we know there are problems, we should be fine, right? I guess it is the nature of technology. Nothing's perfect. But, if we admit that we know about it, maybe the user community will get that warm fuzzy feeling that we care and plan on addressing the issue at our earliest convenience.
All things being equal, I was SEVERELY stressed this week, and my back is revolting in ways that it hasn't done in many months. Fortunately, I have a massage scheduled for today. Hope it helps!