I don't think there's a general answer for it, the question is too broad, and you can't just "adopt a methodology" as if it were a product that you take out of the box, it's something that you evolve over time...but in any case I highly recommend you getting a copy of this book: Head First Software Development
Then you adapt the ideas you like into your project. Don't worry about names and buzzwords, they will be all "passé" next year anyway. Keep it simple at first, adopt the ideas that make more sense and give the most bang for buck, and don't try to solve problems that don't exist yet. It will be a very good start.
For pair programming, at least, it's best to have an even number of programmers... ;P
One of the good things about small teams is that you don't need a lot of support systems to communicate internally (a bugtracker becomes more or less a todo list for yourself, but it's good to have anyway). If having a meeting with the whole team just involves turning around your charir and say "Hey, Bob and Carl, take a look at this!", you don't really need all formal rules of a methology anyway. But agile methods in general is quite well suited to small and medium sized teams, but they require self-motivated team members.
I'll say pick whatever ideas you like from the different methologies, they can be considered suggestions anyway.
For such small teams, I would definitely look at an Agile approach to software development. Personally, I'd probably use a blend of XP, Scrum and Lean, because I know those best. Especially if you are new to Agile, XP provides a good starting point from which you then can find your project-specific adaption. I highly recommend the book "The Art of Agile Development".
My 3 developer team simply uses Kanban + continuous deployments and it keeps us moving rapidly. I've looked at Scrum and others and there's too much overhead for our small team.
They are very close to business side which is bad thing because programmers often do not understand well implications of accounting, time or risk management, etc. Even if they think they do. They see business as another attractive opportunity to improve their sophisticated technical skills. As company is small it is may be overkill to implement complex methodologies inside development team. They can handle technical questions easily themselves. What they cannot handle is understanding that if they are close to business environment does not mean they are not programmers anymore.
I suggest to implement some simple policies which would ensure discipline and focus on technical side rather then talking with customers about technical topics which is what some programmers like so much.
Each team is a blend of personalities and abilities, and each team member is different. Rather than focusing on finding a "methodology" per se, I would recommend that you concentrate on what each team member needs in order to succeed and couple that with what the project needs to succeed. You'll find the right methodology and mix of processes between those two considerations.
As an example, I have been leading a small team (three full-time developers plus some part-time UI designers) for the past seven months. I've found that the following practices/procedures work well for us...
Adopting short (60-90 day), well-defined spirals, which keep the team focused and delivery-oriented and helps us minimize risk.
Adopting an iterative lifecycle, in which we make a few incremental deliveries to the client during the course of a spiral and discuss what we've done. Doing so allows us and the client to ensure that we are addressing their needs.
Tailoring tasking and direction for each team member. For example, one team member is a more junior developer, while the other team member is a very good developer but doesn't handle open-ended tasks well. They require different approaches.
Naturally, I've also tailored CM processes and testing practices to suit the project and the team's needs.
发布评论
评论（6）
我认为没有一个通用的答案，这个问题太宽泛了，你不能只是“采用一种方法论”，就好像它是一个开箱即用的产品，它是随着时间的推移而发展的东西...但无论如何，我强烈建议您获取本书的副本：Head First Software开发
然后你可以将你喜欢的想法应用到你的项目中。 别担心名字和流行语，无论如何它们明年都会“过时”。 首先保持简单，采用更有意义、最划算的想法，不要尝试解决尚不存在的问题。 这将是一个非常好的开始。
I don't think there's a general answer for it, the question is too broad, and you can't just "adopt a methodology" as if it were a product that you take out of the box, it's something that you evolve over time...but in any case I highly recommend you getting a copy of this book: Head First Software Development
Then you adapt the ideas you like into your project. Don't worry about names and buzzwords, they will be all "passé" next year anyway. Keep it simple at first, adopt the ideas that make more sense and give the most bang for buck, and don't try to solve problems that don't exist yet. It will be a very good start.
至少对于结对编程来说，最好有偶数数量的程序员...;P
小团队的好处之一是你不需要很多支持系统来沟通在内部（错误跟踪器或多或少成为您自己的待办事项列表，但无论如何拥有它是件好事）。 如果与整个团队的会议只需要让你的主持人转身说“嘿，鲍勃和卡尔，看看这个！”，那么你实际上并不需要方法论的所有正式规则。 但总的来说，敏捷方法非常适合中小型团队，但需要团队成员自我激励。
我会说从不同的方法中选择你喜欢的任何想法，无论如何它们都可以被视为建议。
For pair programming, at least, it's best to have an even number of programmers... ;P
One of the good things about small teams is that you don't need a lot of support systems to communicate internally (a bugtracker becomes more or less a todo list for yourself, but it's good to have anyway). If having a meeting with the whole team just involves turning around your charir and say "Hey, Bob and Carl, take a look at this!", you don't really need all formal rules of a methology anyway. But agile methods in general is quite well suited to small and medium sized teams, but they require self-motivated team members.
I'll say pick whatever ideas you like from the different methologies, they can be considered suggestions anyway.
对于这样的小团队，我肯定会考虑采用敏捷方法进行软件开发。 就我个人而言，我可能会混合使用 XP、Scrum 和精益，因为我最了解这些。 特别是如果您是敏捷新手，XP 提供了一个很好的起点，您可以从中找到适合您的项目的具体适应性。 我强烈推荐《敏捷开发的艺术》这本书。
For such small teams, I would definitely look at an Agile approach to software development. Personally, I'd probably use a blend of XP, Scrum and Lean, because I know those best. Especially if you are new to Agile, XP provides a good starting point from which you then can find your project-specific adaption. I highly recommend the book "The Art of Agile Development".
我的 3 开发团队简单地使用看板 + 持续部署，它让我们快速前进。 我研究过 Scrum 和其他方法，发现对于我们的小团队来说开销太大了。
My 3 developer team simply uses Kanban + continuous deployments and it keeps us moving rapidly. I've looked at Scrum and others and there's too much overhead for our small team.
他们非常接近业务方面，这是一件坏事，因为程序员通常不太了解会计、时间或风险管理等的含义，即使他们认为他们这样做。 他们将商业视为提高其复杂技术技能的另一个有吸引力的机会。 由于公司规模较小，在开发团队内部实施复杂的方法可能有些过头了。 他们可以轻松地自己解决技术问题。 他们无法理解的是，如果他们接近业务环境并不意味着他们不再是程序员。
我建议实施一些简单的政策，以确保纪律并专注于技术方面，而不是与客户谈论技术主题，而这正是一些程序员非常喜欢的。
They are very close to business side which is bad thing because programmers often do not understand well implications of accounting, time or risk management, etc. Even if they think they do. They see business as another attractive opportunity to improve their sophisticated technical skills. As company is small it is may be overkill to implement complex methodologies inside development team. They can handle technical questions easily themselves. What they cannot handle is understanding that if they are close to business environment does not mean they are not programmers anymore.
I suggest to implement some simple policies which would ensure discipline and focus on technical side rather then talking with customers about technical topics which is what some programmers like so much.
答案是，众所周知，这取决于……
每个团队都是个性和能力的混合体，每个团队成员都是不同的。 我建议您不要专注于寻找“方法论”本身，而是专注于每个团队成员成功所需的内容，并将其与项目成功所需的内容结合起来。 您将在这两种考虑因素之间找到正确的方法和流程组合。
举个例子，在过去的七个月里，我一直在领导一个小团队（三名全职开发人员加上一些兼职 UI 设计师）。 我发现以下实践/程序对我们来说效果很好...
当然，我还定制了 CM 流程和测试实践来满足项目和团队的需求。
The answer is, proverbially, it depends...
Each team is a blend of personalities and abilities, and each team member is different. Rather than focusing on finding a "methodology" per se, I would recommend that you concentrate on what each team member needs in order to succeed and couple that with what the project needs to succeed. You'll find the right methodology and mix of processes between those two considerations.
As an example, I have been leading a small team (three full-time developers plus some part-time UI designers) for the past seven months. I've found that the following practices/procedures work well for us...
Naturally, I've also tailored CM processes and testing practices to suit the project and the team's needs.