Tips and Techniques For Implementing An Agile Program Across Distributed Teams
This tutorial focuses on lessons learned from our experiences in implementing Agile in teams across different time zones in large companies. We will share the pleasure and the pain, ideas that worked as well as ideas that didn’t. We will share what we feel are the critical success factors in making program level implementations successful and sustaining. This is more than an experience report - we share templates, pictures, lessons learned for leveraging technology, managing multiple time zones, recommendations for metrics and reporting, and ideas for future program level success.
This workshop will follow the present-and-discuss format. In our teaching style we trigger the attendees to bring up their questions, issues and hurdles. And we work with these challenges, ensuring that every questions is worked with by the end of the class. The same applies to this workshop, we’ll use facilitation techniques to collect the challenges from the audience, and work with these throughout the workshop. The workshop will be minimal on PowerPoint and maximal on pictures, materials and practices from the teams we worked with.
- Define what an Agile program is; and what it is not, and the need for a program level framework when working across timezones.
- Describe the approach to build a flexible framework for multiple teams to work within. Where do tools fit? What are best practices for sharing learning across teams? How to handle the cultural issues?
- Describe appropriate levels of coaching and training for teams working across multiple time zones. What works? What doesn’t?
- Explain the need for promoting the Agile transition with other departments, manager and senior management.
- Discuss different strategies for implementation: Pilot programs, implementation teams, the role of a PMO.
- Describe some best practices in working with distributed teams.