that can also take away sales of other products from the same company due to the bad rep of the one product. The decision to get it out the door regardless of status is usually only applied when some marketing or management person with little knowledge about what's needed in development pick a date out of the air and advertise that, then push to have people meet it.
I have seen a software project pushed to an advertised completion date that was not realistic with the staffing levels available. The end result was top management decided meeting the date was more important than budget, so overtime was approved and the project team worked ten hours a day, six days a week for two months to get the project completed and properly tested by the deadline - fully tested product delivered seven days before the deadline, allowing sufficient time for full deployment to the hardware before the units involved shipped out to the troops in the field. It showed it can be done properly, but you have to take the hit is someone announces or sets an unrealistic time frame. No one liked working 60 hours weeks for two months solid, but they all got 4 weeks paid leave as a bonus on top of the overtime payment that almost doubled their weekly pay, and all for digging in and helping dig the ultra top brass out of their stupidity.
Keep Up with TechRepublic