小团队：在特定对象上工作还是在特定层上工作更好？
我是一个小团队的领导者，我想要一些关于如何为 n 层业务软件的开发人员分配任务的建议。
场景 A：
每个开发人员都有一些特定的对象要在所有层上构建（DB、DAL、BL、GUI...）
场景 B：
每个开发人员都有特定的层域要在任何对象上工作！
场景 C：
每个开发人员都按照特定的时间表处理任何事情！
任何建议都会有所帮助！ 谢谢
I'm a leader of a small team, and I want some advice of how to divide tasks on developers of a n-tier business software.
Scenario A:
each developer has some specific objects to build at all layers (DB, DAL,BL, GUI...)
Scenario B:
each developer has a certain domain of layers to work on at any object !!
Scenario C:
each developer work on anything with a specific schedule !!
any advice would help!
thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您应该考虑每个团队成员的知识技能和经验，并相应地分配工作。
如果您的设计正确分层和分解，那么任何人在等待其他人时都应该没有问题，因为他们可以轻松地删除丢失的类并继续他们的工作。
如果时间允许，您可能希望将部分工作分配给不熟悉系统某些领域（业务领域或编程相关）的成员，以便他们能够学习这些领域，并及时成为全面发展的程序员但是，如果有更多的团队成员熟悉系统的各个领域并对业务领域有深入的了解，那么业务将会受益。所以这对每个人来说都是双赢的（只要投入时间）。
You should take into account the knowledge skills and experience of each of your team members and divide the work accordingly.
If your design is correctly layered and decomposed then there should be no problem for anyone as regards waiting on someone else since they can easily stub out the missing class(es) and continue on their work.
If time permits, you may want to assign some portions of the work to members who are not familiar with certain areas of the system (either business domain or programming related) so they can learn those areas and in time not only become well rounded as programmers but the business will benefit by having more the one team member being familiar with various areas of the system as well as having a deep understanding on the business domain. So it's win-win for everyone (with an investment of time).