or in the case of personal experience, trying it on during estimation to ramp up the estimate to feasibly unrealistic time frames with the expectation that the customer will negotiate it down. Unless the customer is on the ball, they end up paying the same for less. Some developers almost seem to believe that it is almost de rigueur that defects should be there and can be (system tested out) - there is no ethos about striving for zero defects. As long as the customer is paying, all is good
Biting the hand that feeds IT
