How to be Successful with Distributed Agile Teams

Your development team may be distributed around the world, around the country, around the metro area, or around your building. No matter the situation, there are tools and techniques that you can use to shrink the distance, shift the timezone, and collaborate on the work. In this talk, I'll go over a variety of philosophies and practical approaches for enabling your distributed teams to be successful with Agile.

 
 

Outline/Structure of the Talk

  1. Introduction, who am I, why do I know this stuff
  2. Reasons for distributed agile development
  3. Philosophical Considerations
    1. Structuring a remote team
    2. How remote do you want to be?
    3. What's important? Maintenance? Cutting-edge development? Other?
  4. Tools and Techniques
    1. Culture
    2. Communication
    3. Messaging
    4. Timeboxing aka Don't waste people's time!
    5. Core hours
    6. XP
    7. Sprint management, tracking, ceremonies
    8. Story Pointing
    9. Backlog refinement
    10. Prioritized attendance at ceremonies based on role
  5. Summary
  6. Q&A

Learning Outcome

You'll leave this talk with a set of ideas and tools to potentially use in your own distributed agile environment.

Target Audience

You'd probably benefit from this talk if you are 1) getting ready to work with one or more distributed agile teams, 2) currently working through the challenges of collaboration and communication in an agile environment, or 3) looking for ideas to sharpen

Prerequisites for Attendees

This talk assumes that you are familiar with agile concepts like reviews and retros, but mostly bring your awareness of your current (or looming) distributed agile situation.

schedule Submitted 2 years ago

Public Feedback

    help