Back to List

Distributed Global Challenges (Agile Transformation Pain Point #19)

Rachael Wilterdink Rachael Wilterdink  |  
Jan 24, 2019
So far, I've been primarily discussing co-located teams, which is ideally better. However, this is the real world, and it's a global economy – most people don't have the luxury of being co-located.
distributed global challenges

If you have a team with dispersed team members, set up your working rules so that you have some time that overlaps with one another. It could be an open conference line, audio line, or video conferencing. Just make sure you have a time where you’re all able to be together in some way.

Make the most of your tools

If you have technology tools, make the most of them. Most companies nowadays have some sort of video conferencing. Audio is great, but everyone knows that video allows you to see body language, and that's going to feel a lot more like you're together. You can read between the lines. Not everything always comes through if you're just on the phone. If it's at all possible to use videoconferencing, that would be even better.

Also, use collaboration tools. Slack is a great one. I really like Microsoft Teams. There's even SharePoint and Skype. Use anything that lets you smoothly communicate with your team.

Encourage collaboration

If you do have the privilege of being co-located, don't just sit in your cubicle facing the corner. Turn around, talk to your team, build a collaboration space, get rid of the walls, and put a table in the middle so you can just turn around and have impromptu meetings. That will allow you to be more creative and innovative.

The fewer walls you have between you, the more knowledge transfer is going to happen in a very natural way. You’re not going to feel like you're cross-training, but you’re going to pick things up just by being near people as other conversations are going on.

Get the free eBook

This is the nineteenth of 20 blogs on 20 Agile Transformation Pain Points (and how to avoid or manage them). To read them all right now, download our free eBook.
agile transformation pain points ebook


Love our Blogs?

Sign up to get notified of new Skyline posts.


Related Content

Blog Article
Skipping Inspection and Adaptation (Agile Transformation Pain Point #20)
Rachael WilterdinkRachael Wilterdink  |  
Jan 31, 2019
Inspecting and adapting is one of the key parts of agile and Scrum. But over time, teams start to feel bored as if every session is the same.   If it does become boring, make sure you switch it up to keep it fresh. The Fun Retrospectives website has lots of ideas. Don’t skip this...
Jan 29, 2019
Jen Kalz is Featured on Mastering Business Analysis Podcast

We are excited to announce that Jen Kalz, Managing Consultant, is a featured guest on today's Mastering Business Analysis Podcast. Jen has known Dave Saboe, the man behind the Mastering Business Analysis site and podcast, for the last several years. She and Dave often speak at the same...
Blog Article
Accruing Technical Debt (Agile Transformation Pain Point #18)
Rachael WilterdinkRachael Wilterdink  |  
Jan 17, 2019
Everyone who works in technology probably knows that you already have a big pile of technical debt. The problem is that you are going to have to eventually pay that bill, and some of it is risky.     Dig out a little every Sprint You really need to be careful about technical...
Blog Article
Focusing On Projects Rather Than Products (Agile Transformation Pain Point #17)
Rachael WilterdinkRachael Wilterdink  |  
Jan 10, 2019
This is a difficult transition for waterfall companies to wrap their heads around. It's a big mindset shift that needs to happen to be truly successful. I'm not saying that you can't have an agile Scrum team that works on projects with a distinct beginning and end. That might be a...
Blog Article
Skipping Over Quality (Agile Transformation Pain Point #16)
Rachael WilterdinkRachael Wilterdink  |  
Jan 03, 2019
You should not skip over quality because it’s inherently meant to be baked into agile. There are many ways you can do that. You could consider doing acceptance test-driven development, behavior-driven development, or you can write automated tests wherever possible. Again, I really like the...