Tips Agile successfully distributed making
Purists and hipsters Scrum will argue that distributed teams in agile communities of practice are taboo.
1. Decide how to distribute
Teams work differently in their remote locations, but the whole team synchronized officially at least once a day, but also ad hoc as situations require it;
ACH employees at each site has all the necessary skills to meet the dedicated Sprint Backlog;
People who should be encouraged to work as a team, as a team in the country over in different cities, and the other in country B;
2. Create the viscosity or consistency
We want to get teams together which requires a clear vision;
So we recognize that cultures differ in our team - we make foster cooperation and caring relationship at the beginning of the project to the subcultures;
Actively working structures and tactical team to strengthen;
Build trust through timely communication of progress
3. You need to change the way you communicate
In Cinderella Project (a perfect project) would come together a team from different places to meet, socialize and form of cohesion;
We encourage teams for at least one iteration to stay together;
Learn the lay of the land
Make will be used with the "flavor of Agile '(for example, all work together teams to assess, implement and communicate differently - meet these properties - make or break your Agile Initiative) must organize cross quarterly visits either the entire team or people travel by pollinate between sites ensure the investment in the concept of the Ambassador team with the people, the good work relations
A wiki culture or information sharing philosophy will be very important, more than with co-located teams
They are the absence of key people need more meat on this product backlog of physical counters
Horizontal communication should be encouraged and unit
The distance is not such a problem, the time zones!
"If the transition to a distributed team, err on the excessive communication side."
You must ensure that its technology supports their diversity
Use Agile Lifecycle Management tools like Jira, VersionOne etc.
Use video tools and appropriate high-quality voice videoconference successfully and the gap to bridge distance will help to design whiteboards online sessions cooperation
A Retrospective online tool that the way to ensure the improvement is not lost