Well, to me, your actual configuration is much more appropriated for Agile than a 300+ developer shop (not really sure how Agile was implemented there, I'd love to hear more about that as scaling to that size requires a very high level of maturity on Agile IMO).
So, my answer would actually be: starting with 4 people, all values and practices are appropriate and valuable. Actually, what Agile methodology did you adopt previously? What practices did you implement? What makes you think they wouldn't be appropriate?
PS: If I may, try to see beyond engineering practices, Agile is not (just) about that (this is especially true for Scrum). Practices such as Test Driven Development, Continuous Integration, etc are nice but they are just a mean, not an end. They won't suffice for a successful Agile implementation. Agile is a business oriented organizational pattern. In other words, technical stuff is not really the best starting point when implementing Scrum, you should start with organizational things.
IMHO all of the development practices are appropriate. In fact, for a long time an agile team was expected to be a small teams (5-9 people). There is an artile of infoq about it.
Also, because you have a small team both communication and collaboration will become easier, so the practices would work even better.
Focus on introducing practices that add the most value to the team.
As the team is small impact of the change will be highly visible, if you work with the team and show improvements then you can go back and add another one - again the one that add the most value to the team.
One of the most important thing is that the projects are approached with an agile mindset, adding tools & techniques in the context of long projects that can't adapt to change & are not highly tuned with the customer won't have the ultimate result that you should be aiming for.
I think you may want to flip the question around; what agile methods would not be suitable because you are a small team. I am no expert in agile practices, but I can't really think of any that would not be appropriate because of your team size.
发布评论
评论（5）
好吧，对我来说，您的实际配置比 300 多个开发人员商店更适合敏捷（不太确定在那里如何实施敏捷，我很想听到更多关于这一点的信息，因为扩展到该规模需要非常高水平的IMO 上敏捷的成熟度）。
所以，我的答案实际上是：从 4 个人开始，所有的价值观和做法都是适当的和有价值的。实际上，您之前采用了什么敏捷方法？您实施了哪些实践？是什么让您认为它们不合适？
PS：如果可以的话，请尝试超越工程实践，敏捷不仅仅是这样（对于 Scrum 来说尤其如此）。测试驱动开发、持续集成等实践很好，但它们只是手段，而不是目的。它们不足以成功实施敏捷。敏捷是一种面向业务的组织模式。换句话说，技术性的东西并不是实施 Scrum 的最佳起点，你应该从组织性的东西开始。
Well, to me, your actual configuration is much more appropriated for Agile than a 300+ developer shop (not really sure how Agile was implemented there, I'd love to hear more about that as scaling to that size requires a very high level of maturity on Agile IMO).
So, my answer would actually be: starting with 4 people, all values and practices are appropriate and valuable. Actually, what Agile methodology did you adopt previously? What practices did you implement? What makes you think they wouldn't be appropriate?
PS: If I may, try to see beyond engineering practices, Agile is not (just) about that (this is especially true for Scrum). Practices such as Test Driven Development, Continuous Integration, etc are nice but they are just a mean, not an end. They won't suffice for a successful Agile implementation. Agile is a business oriented organizational pattern. In other words, technical stuff is not really the best starting point when implementing Scrum, you should start with organizational things.
恕我直言，所有的开发实践都是合适的。事实上，长期以来，敏捷团队都被认为是小团队（5-9 人）。 infoq 有一篇关于它的文章。
此外，因为你有一个小团队，沟通和协作都会变得更容易，所以实践会效果更好。
IMHO all of the development practices are appropriate. In fact, for a long time an agile team was expected to be a small teams (5-9 people). There is an artile of infoq about it.
Also, because you have a small team both communication and collaboration will become easier, so the practices would work even better.
重点介绍可为团队增加最大价值的实践。
由于团队规模较小，变更的影响将非常明显，如果您与团队合作并表现出改进，那么您可以返回并进行改进添加另一项——同样是为团队增加最大价值的一项。
最重要的事情之一是以敏捷的心态来处理项目，添加工具和工具。在无法适应变化的长期项目背景下的技术没有与客户高度协调就不会获得您应该追求的最终结果。
Focus on introducing practices that add the most value to the team.
As the team is small impact of the change will be highly visible, if you work with the team and show improvements then you can go back and add another one - again the one that add the most value to the team.
One of the most important thing is that the projects are approached with an agile mindset, adding tools & techniques in the context of long projects that can't adapt to change & are not highly tuned with the customer won't have the ultimate result that you should be aiming for.
公共代码审查，无论每个人是否都在同一个站点上
Communal code-review whether or not everyone is on the same site
我想你可能想反过来问这个问题；由于您是一个小团队，哪些敏捷方法不适合。我不是敏捷实践方面的专家，但由于您的团队规模，我真的想不出任何不合适的做法。
I think you may want to flip the question around; what agile methods would not be suitable because you are a small team. I am no expert in agile practices, but I can't really think of any that would not be appropriate because of your team size.