问题描述
我正在从事一个软件项目，该项目的几个成员在家中工作，而另一些则是兼职人员。我们至少每个月会面一次。我们主要通过电子邮件交流。我们的源代码存储库（Mercurial）位于我们共享的丛林磁盘（工作组）上。
I'm working on a software project which several members are working from home and some other are part-timers. We meet physically one time each month at least. We communicate mostly by emails. Our source code repository (mercurial) is on a jungle disk (workgroup) that we share together.
我们有一个有效的产品和一个客户。但是，我们还不够敏捷（即：代码中的一项更改有时会破坏其他东西，我们没有单元测试，代码没有文档等），我想使用一种敏捷方法来协调我们的工作并跟踪我们的进展。我也想使用TDD。
We have a working product and one customer. But, we are not agile enough (ie: one change in the code sometimes break something else, we don't have unit testing, code is not documented, etc.) I want to use an Agile methodology to coordinate our work and track our progresses. I also want to use TDD.
团队没有敏捷方法（或其他方法）方面的经验。
The team has no experience with agile methodologies (or other methodologies).
将敏捷方法与地理上分散的团队一起使用的最佳方法是什么？哪种方法最适合那种团队？
What is the best approach to use an Agile methodology with a geographically distributed team? Which methodology is best with that kind of team? How to implement it efficiently with the least resistance possible?
谢谢！
推荐答案
我是分布式XP团队的一部分，在三个站点之间共享源代码和故事，每个站点相距12小时（西雅图，英国伯恩茅斯和新加坡）。
I have done this as part of a distributed XP team sharing source code and stories across 3 sites, each site being 12 hours apart (Seattle, Bournemouth UK, and Singapore).
以下是我们所做工作的一些记录：
Here are some write-ups of what we did:
- 分布式敏捷模式：
- Distributed Agile Patterns: http://www.keithbraithwaite.demon.co.uk/professional/papers/index.html#europlop2005
- http://www.keithbraithwaite.demon.co.uk/professional/papers/index.html#xp2005
我们发现，在项目开始时使每个人都聚在一起有助于建立标准
We found that it helps to get everybody physically together at the start of the project to establish standards and to build relationships.
我们还发现，这有助于拥有大使 -在团队之间运送不同的人来传播知识和积累知识
We also found that it helps to have "ambassadors" - shipping different people around between teams to spread knowledge and build trust.
我们很幸运地拥有三个站点，每个站点相距12小时-因此我们可以在上午的第一件事和最后一件事中举行一次站立会议。晚上。我们称它们为交接会议 ，并通过来访团队和离任团队之间的视频会议来进行他们的通话。
We were lucky to have three sites that were each 12 hours apart - so we could have a stand-up meeting first-thing in the morning and last thing in the evening. We called them "hand-over meetings" and did them over video-conference between the incoming team and the outgoing team.
我们还发现远程结对编程工作-在本地对和远程对（即四个人）之间进行，但是它非常紧张且耗费大量资源，并且最好仅在很短的时间内完成，这对于查看其他人真的很重要
We also found remote pair-programming worked - between a local pair and a remote pair (i.e. four people) but that it's very intense and draining and best done only for short periods of time when it's really critical to see what other people are doing remotely.
另外：肯特·贝克（Kent Beck）对使用Eclipse进行远程配对的人的建议：
Aside: Kent Beck's Advice for people using Eclipse to remote pair: http://www.threeriversinstitute.org/blog/?p=584
这篇关于如何在地理位置分散的团队中使用敏捷工具/方法的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！