Yea, Im on the other end of the spectrum: So IDP integrates with SN, OHS, ADP, RDC, Xym. The support is managed by the SSD, DC2 (and many, many more....). I think the Project and Product managers make these up to prove they are doing something productive. So many acronyms, and no documentation except the main project docs. So you need to read a mountain of documentation to even know what people are talking about. Even better when you have IDP, ADP, EDP etc and people from several different countries trying to pronounce all of these correctly.
My personal naming rules are "one unemotive word, two syllables max, with clear unambiguous spelling and pronunciation". Maybe go to three syllables if it's really fitting. Generally the name is not meant to reflect the function - the point is to be memorable, not descriptive (and not customer facing). This being said, I'm a small company guy, so I haven't run into the need for amazing amounts of acronyms or product names (I'm not sure how far my rules would stretch...)
My favourite shortening was a netadmin friend of mine who worked at a bank a while back, describing coding schemes for network hardware: "blah blah ethernet concentrator blah address blah city makes XXXECO1" => "What's an 'ethernet concentrator'?" => "Is it a switch? Is it a hub? Is it (*rattles of a couple of other things I can't recall)? Who cares? They do similar things in the grand scheme..." And shorten down to a clear 'EC' to cover them all.
