"include go/no-go meetings"
I've seen one circumstance where it should have been no-go right from inception. However the project owner was the senior IT manager so it was go all the way in moving an application to a completely new OS as far as the RDBMS & tools vendor was concerned (I was later told their porting procedure was something along the lines of "we made the changes necessary to get it to compile"; I suspect we were the only site that went live).
In practice as soon as we got to go-live we started to get database index corruption; I suspect there was a race condition that only manifested itself under real load. Oddly enough, migration back to the sort of OS it should have been on had weeks of testing mandated with no issues found then or on go-lie. I could have done without those weeks of testing as they were weeks of fire-fighting on the live system as far as I was concerned.
Biting the hand that feeds IT
