{'fraction_non_alphanumeric': 0.02729528535980149, 'fraction_numerical': 0.004962779156327543, 'mean_word_length': 5.022388059701493, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Lessons Learned from Leading Workshops about Geographically Distributed Agile Teams

We've been teaching workshops about geographically distributed agile teams together and separately since March 2011. In that time, we've led workshops in New Zealand, Australia, Israel, Germany, and multiple times in the US, Saudi Arabia, and Canada. But it doesn't matter where we hold these workshops or where the project leaders or the company senior managers are located, we hear many of the same stories. The players vary, the context is often different, but underneath it all, we've seen a set of common mistakes and success factors. In this article, we bring these common aspects together into a set of lessons learned, with some concrete advice on how to avoid the mistakes and leverage and amplify the successes.