The fact that Jazz is a distributed development effort (8 locations?) and that you are self hosting is a great test for the tool and shows that it can work for a real development team. What I'm wondering though is whether you've done any work on network monitoring within your environment or on other non-functional test environments?

Specifically, WAN network links between geographically distributed teams tend to have lower bandwidth, higher latency and higher risk of packet loss. IBM Rational's approach to this in the past has been the use of ClearCase/ClearQuest multi-site, which we've found to be incredibly effective even on reasonably poor networks.

The approach that TeamConcert/Jazz is taking is one of a single server; and although I appreciate that the team server can be deployed on WebSphere, that's not going to help with poor network scenarios. Therefore, I was wondering if you've been doing any work to be able to provide guidance on typical network characteristics that would be required to run a Jazz based collaborative environment. Benchmarks from your own networks would be a great starting point and other recommendations for typical development teams would be a great follow up.

To put this into perspective, if the Jazz teams have 10 Mbit connectivity and 50ms latency then you're an order of magnitude better than those of us restricted to a Megabit and 500 ms latency at best between teams.