Java Programming

Like many large organizations which experience mergers, mine is grappling with a confluence of different workflow methods, programmatic paradigms (Java vs .Net vs Flex vs Etc.), and general opinions on "how things ought to be done," even down to the level of whether a particular product should be desktop software or web-based.

High-level executives tend to rely on their technical counterparts to provide them with a sense of direction in regards to such matters, but what happens when there are many technical counterparts, with differing opinions? Well, gentle reader, DISCORD happens.

So I come to you all as a form of venting, and also to get your honest opinion on such matters.

Group A says: "Group B doesn't produce results fast enough, they should be using XYZ methodology."
Group B says: "That might work for Group A, but that doesn't mesh with what we develop and the needs of our customers."

Group C says: "For products like this in an environment like that, using .NET and Visual Studio would be the best for RAD."
Group D says: "To heck with Group C, Java is the way to go for RAD, whether developing web-based apps or Windows desktop apps."

What are your thoughts on the above opinions?

Additionally, some say that XYZ method works best for large teams, but not for small teams. Others say if it works for one, it will work for all. What about you? Do you think certain project sizes work best with certain methods? Is a methodology that works for a lone programmer on a small project the best methodology for a large team working on a massive project?

Lastly, are there any particular methodologies that have functioned particularly well with you and vice versa? Why and why not?

Thanks folks! I appreciate your insight.

Edited by: user8825851 on Jul 8, 2011 1:06 PM