no sense of timing

[rone]

"There are radical changes between beta 2 and [the release version]." Am i crazy, or is the period between your second beta and your release version probably NOT the best time to make "radical changes" to your software?

Comments

[simbuttercup.livejournal.com]

Um, well, my experience at my present company indicate not. I still can't even get anyone around here to admit that our 29 Mar. 2002 ship date has passed so we've missed our deadline.

ME: So, Project Manager, what is our new deadline?

PM: ::startled:: New deadline? What's wrong with our old one?

ME: Well, you see, um, it's kinda May and the old one was kinda March. I think we may have slipped.

PM: ::relieved:: Don't worry about it, we'll be fine. And would you mind whipping up a Java API Guide for the release? We've decided to put out a Java version for the first time.

QA: We've changed the scope of testing to encompass the entire software package rather than just the independent component. That'll make it so that we'll risk missing our deadline, but we should just barely squeak it through a day early. That'll leave deadline day secure so we can head out to Don Giovanni's and get pasta and wine! Yippee! We're making our deadline!

ME: Uh ... Okay.