I've spent several years working in fully distributed agile teams and I've learned that the distributed setting highlights the need to get to the essence of agility. Having then spent time with co-located teams that profess to be agile I've found that applying the distributed mindset can help break the often in-grained and dysfunctional approaches that sometimes foster. So, what I may have thought of as being a limiting factor in distributed development before, I have now found to be an advantage. I think there are some interesting ideas that I can put forward. Learning outcomes would be: * how distributed agile techniques can be applicable in a co-located setting * how going distributed can be an effective way to address problems in a non-agile stagnating culture * there is a balance that can be reached after the initial switch to a distributed approach Part of the talk will be to present recipes that work well in a distributed setting and then explore why that's the case and then suggest how that might help the general case. The underlying theme here is that the more 'extreme' the setting the more important it is to get to the real essence of agility in order to succeed. By doing this we learn how to be more agile in general.
Sign in to add slides, notes or videos to this session