Well, as far as source control goes, somebody needs to take the lead and set up the basic structure of the project, directories, etc. and communicate it to the team. On projects I work on, this is usually an architect or senior developer, someone who knows the best practices for project organization for the team/company.
With respect to avoiding having multiple people working on the same tasks, that's a project management function; someone needs to determine what tasks need to be done, and communicate it to the team. If you are working in an agile/scrum environment, the team may divide and hand out work items amongst themselves, but in either case you need to communicate to avoid doing the same work twice.
EDIT
To address the issue of multiple people working on the same task, I tend to work on smaller teams, 2-6 people; in this environment, I have had a lot of success with a scrum-influenced approach using the Crystal Clear methodology:
Architect(s)/designer(s) come up with high level design
Architect(s)/designer(s) define iterations/deliveries, the first of which is a "project skeleton" which consists of architectural and back-end components and a thin slice of the app
Lead person breaks up features into 1-3 day tasks/units of work (estimated)
Team meets and discusses priority, timing and dependencies of tasks, and divides up the first set of tasks
The team has brief daily meetings to discuss status/priorities and dependencies, and change direction if necessary
With larger projects/teams, you will almost certainly need someone whose main job is dedicated to tracking status, dependencies and conflicts.
I don't think source control has much to do with the problem of coordinating people's efforts (except that it can catch some "conflicts" when people erroneously try to modify the same files in different ways -- but, that's not as good as preventing conflicts, and even just "preventing conflicts" does not per se ensure that everybody is working on what they should ideally be working right now, in terms of priorities). Coordination is properly managed with practices (and perhaps tools, e.g. Pivotal Tracker -- but, using the right practices is even more important than using nice tools!-) that specifically focus on ensuring coordination. For example, the practices that Tracker is designed to support and enhance, such as story-based iterative planning, and other compatible ones, such as stand-ups, offer ways to meet these needs.
You must be having a base version that everyone is using, check that into the repository, and then make incremental changes to the repository, make sure that everyone works on different part of the code, commit every working change, and resolve conflicts as and when they occur. That is how I would do it.
发布评论
评论（3）
就源代码控制而言，需要有人带头建立项目、目录等的基本结构，并将其传达给团队。在我从事的项目中，这通常是架构师或高级开发人员，他们了解团队/公司项目组织的最佳实践。
避免多人执行相同的任务，这是项目管理的职能；需要有人确定需要完成哪些任务，并将其传达给团队。如果您在敏捷/Scrum 环境中工作，团队可能会在彼此之间划分和分发工作项目，但无论哪种情况，您都需要进行沟通以避免重复执行相同的工作。
编辑
为了解决多人执行同一任务的问题，我倾向于在较小的团队中工作，2-6 人；在这种环境下，我通过受 scrum 影响的方法取得了很大的成功使用 Crystal Clear 方法：
对于较大的项目/团队，您几乎肯定需要一个主要工作致力于跟踪状态、依赖性和冲突的人。
Well, as far as source control goes, somebody needs to take the lead and set up the basic structure of the project, directories, etc. and communicate it to the team. On projects I work on, this is usually an architect or senior developer, someone who knows the best practices for project organization for the team/company.
With respect to avoiding having multiple people working on the same tasks, that's a project management function; someone needs to determine what tasks need to be done, and communicate it to the team. If you are working in an agile/scrum environment, the team may divide and hand out work items amongst themselves, but in either case you need to communicate to avoid doing the same work twice.
EDIT
To address the issue of multiple people working on the same task, I tend to work on smaller teams, 2-6 people; in this environment, I have had a lot of success with a scrum-influenced approach using the Crystal Clear methodology:
With larger projects/teams, you will almost certainly need someone whose main job is dedicated to tracking status, dependencies and conflicts.
我不认为源代码控制与协调人们的努力有太大关系（除了当人们错误地尝试以不同方式修改相同文件时它可以捕获一些“冲突”——但是，这不如防止冲突，甚至只是“预防冲突”本身并不能确保每个人都在做他们现在应该做的事情（就优先事项而言）。通过实践（也许还有工具，例如 Pivotal Tracker）正确管理协调 - 但是，使用正确的实践是甚至比使用好的工具更重要！-) 特别注重确保协调。例如，Tracker 旨在支持和增强的实践，例如基于故事的迭代规划，以及其他兼容的实践，例如 站立会议，提供满足这些需求的方法。
I don't think source control has much to do with the problem of coordinating people's efforts (except that it can catch some "conflicts" when people erroneously try to modify the same files in different ways -- but, that's not as good as preventing conflicts, and even just "preventing conflicts" does not per se ensure that everybody is working on what they should ideally be working right now, in terms of priorities). Coordination is properly managed with practices (and perhaps tools, e.g. Pivotal Tracker -- but, using the right practices is even more important than using nice tools!-) that specifically focus on ensuring coordination. For example, the practices that Tracker is designed to support and enhance, such as story-based iterative planning, and other compatible ones, such as stand-ups, offer ways to meet these needs.
您必须拥有每个人都在使用的基本版本，将其签入存储库，然后对存储库进行增量更改，确保每个人都在代码的不同部分上工作，提交每个工作更改，并及时解决冲突它们发生了。我就是这么做的。
You must be having a base version that everyone is using, check that into the repository, and then make incremental changes to the repository, make sure that everyone works on different part of the code, commit every working change, and resolve conflicts as and when they occur. That is how I would do it.