As an Agile community, one would think that remote teams are a given; that they should just work. Isn’t that what Agile is all about? Self-organizing? Making different situations work? Nine times out of ten we hear from Agile practitioners that remote teams just don’t work – that the chasm is too deep to bridge and that it just doesn’t work if everyone isn’t together. Our coaches started working with teams in an age before the technology conveniences that we have now. As such, we are always baffled by people who say “remote teams don’t work” especially since we as an organization span several time zones.
Who Should Attend
This workshop is open to all attendees interested in learning how to support their remote teams or introduce a healthy culture of remote work to an organization.
Half-Day (4 hours)
No prior Agile experience necessary.
- Setting the Stage – Where are we now?
- Working Definition of Remote Work
- Pros and Cons of Remote Work
- Us vs. Them Mentality
- Path to Successful Remote Teams
- Corporate Remote Work Policy
- Team Work Agreement
- Communication Plan
- Building Your Remote Work Toolkit
- Action Plan, Takeaways, and Next Steps
- Define remote work for your current environment by listing the options that could be made available to teams.
- Identify the pros and cons of remote work by completing a shared table-top exercise.
- Recognize how to identify the “us vs. them mentality” and avoid this bias by identifying current biases in your current environment.
- Create a path to successful remote teams by writing a remote work policy, sample team work agreements, and a communication plan.
- Start the foundations of a technical toolkit to support remote work by identifying the tools already available and completing an analysis for future technology needs.