Earlier quoted context omitted.
Always when you hear the word "Enterprise" and it's not related to Star Trek it usually means "company that has made it so far and so stable up on the food chain that from now on they don't need to work hard anymore". If you have never worked in Enterprise software development, think about putting 100 first semester students into a room full of drugs and costumes and then letting them act "professional". What do you…
Amusing, but the issues with Enterprise Software are far more complex than that. Having spent my career working with Enterprises of one sort or another, here are a few off the top of my head: 1. You are not the customer. With ad-driven products, we have painfully realized that if we aren't paying, we aren't the customer, and when something seems awful to us, the explanation often lies in the fact that the thing that…
Yes, and depending on the enterprise, these "big features only there to justify high costs" may not actually be needed or useful or relevant. It might be 'OK' to have a bunch of interns slap something together, if it only needs to be "real" enough to look pretty and look functional in a few demos or in a few specific happy-day cases.
Analytics and Reporting is probably the most common example I've seen of this -- it's not a bad feature on it's own, but companies will sometimes pay top dollar for it, even in places it makes no sense and/or will never get used. If that gets delivered in a broken/unusable state, it's "ok" because the customer will never actually click that button anyway.
----
If "New Skype" is "enterprise communication support" in a corporate feature list (and not a real product filling a real need, as it used to be) then I can see how a broken or unusable Skype could still be a 'success' for Microsoft.
Note: I don't agree with any or support any of this. But I've seen this play out in real life enough to know it happens.