@KingDuken If marketing is asking for feedback on the requirements document in the production phase, you have a problem.

@ThePhoton Well actually they're instructions documents of how to setup our hardware, shell commends, maintenance troubleshoot, etc. They just want to make sure we included everything.

We're about to announce a product next week but we're technically in production phase now.

@KingDuken Do you have a "PDR" phase review? It's supposed to be when management decides to start "investigating" a project. Later there will be a "IDR" (investigation to development) which is supposed to be approval to start actual product development. But somehow, in our organization, if you don't have the design 90% complete at PDR, it's not going to get approved.

@ThePhoton We do. Sometimes we've been stuck in prerelease purgatory where our "bring up" engineers don't feel comfortable about moving on. I've actually caused this one time at work not too long ago lol. One our PMs asked me to beta manage a prerelease product to send to Motorola (because Motorola was curious about what we were making so we let them demo that product for their sake)... and I found soooo many problems.

I was like, "Um... Excuse me guys but this build of this hardware is absolutely garbage... There are missing devices on the I2C buses, the DIMMs our vendors gave us causes the CPU to overheat, the BIOS tends to corrupt on every cold boot... How did we get this far into development?!" So we had to go to VP2 to VP2.1 haha.

VP is a preproduction phase