> how do we know they didn't account for it when they buffered initially? Maybe they had a different internal timeline (end of aug) vs. an external timeline.
If they were like practically everyone else in this wacky industry, they would be late for the internal timeline but not worry about it because the external timeline is the one that matters. Thus, there would be very little pressure to meet the internal timeline and a lot of pressure to meet the external timeline. Worse, they would wind up being late for the external timeline as well as the internal timeline.
For example, if someone wanted to add a feature to Snow Leopard, the dev team might say "we can't make our internal schedule if we add this." But some product manager would say "well, will you still make the external schedule?" and bang they would start to slip.
If they had an internal schedule and managed to stick to it I believe they are an exception to how software is usually developed.
If they were like practically everyone else in this wacky industry, they would be late for the internal timeline but not worry about it because the external timeline is the one that matters. Thus, there would be very little pressure to meet the internal timeline and a lot of pressure to meet the external timeline. Worse, they would wind up being late for the external timeline as well as the internal timeline.
For example, if someone wanted to add a feature to Snow Leopard, the dev team might say "we can't make our internal schedule if we add this." But some product manager would say "well, will you still make the external schedule?" and bang they would start to slip.
If they had an internal schedule and managed to stick to it I believe they are an exception to how software is usually developed.