I don't know if this has been discussed.
我不知道是否已经讨论过这个问题。
Let's say you are in a three developer team. How would you share:
假设您是一个三开发团队。你会如何分享:
- models - views - controllers
- by controllers
- by use cases
- something else?
模型 - 视图 - 控制器
用例
Maybe someone says this has nothing to do with asp.net mvc but I think it affects somehow.
也许有人说这与asp.net mvc无关,但我认为它会以某种方式影响。
3 个解决方案
#1
3
Do it by story. But by far the best way is have 2 developers work on the same story. Working together across the whole architecture. They can share the tasks as they are needed, creating the view or the model or the stored procs, and tables etc. There will be some stepping on toes but at those times they can pair program. Try to think of the 'team' doing a story. Rather than a single developer, and if they all work on the same story at the same time, the development should flow at a cracking pace. As Kieron says, you need a ten minute design meeting with the whole team, to decide how its going to hang together.
通过故事来做。但到目前为止,最好的方法是让2名开发人员在同一个故事上工作。在整个架构中协同工作。他们可以根据需要共享任务,创建视图或模型或存储的过程,表格等。脚趾会有一些踩踏,但在那些时候他们可以配对程序。试着想一下“团队”做一个故事。而不是一个开发人员,如果他们同时在同一个故事上工作,那么开发应该以一种快速的步伐流动。正如Kieron所说,你需要与整个团队进行十分钟的设计会议,以决定它如何挂在一起。
#2
2
We break it up like this:
我们这样分解:
Team A:
- Views
- CSS
- JavaScript
Team B:
- Controllers
- Models
- Database
We use Mind Mapping applications to work out what Controllers and Views we need first, so the whole team knows how to tie things together.
我们使用Mind Mapping应用程序来确定我们首先需要的控制器和视图,因此整个团队知道如何将事物联系在一起。
It's worked brilliantly for us, increased our productivity substantionally.
它对我们来说非常出色,大大提高了我们的生产力。
#3
1
By use case or task. Helps spread the knowledge about the entire process around.
通过用例或任务。帮助传播有关整个过程的知识。
#1
3
Do it by story. But by far the best way is have 2 developers work on the same story. Working together across the whole architecture. They can share the tasks as they are needed, creating the view or the model or the stored procs, and tables etc. There will be some stepping on toes but at those times they can pair program. Try to think of the 'team' doing a story. Rather than a single developer, and if they all work on the same story at the same time, the development should flow at a cracking pace. As Kieron says, you need a ten minute design meeting with the whole team, to decide how its going to hang together.
通过故事来做。但到目前为止,最好的方法是让2名开发人员在同一个故事上工作。在整个架构中协同工作。他们可以根据需要共享任务,创建视图或模型或存储的过程,表格等。脚趾会有一些踩踏,但在那些时候他们可以配对程序。试着想一下“团队”做一个故事。而不是一个开发人员,如果他们同时在同一个故事上工作,那么开发应该以一种快速的步伐流动。正如Kieron所说,你需要与整个团队进行十分钟的设计会议,以决定它如何挂在一起。
#2
2
We break it up like this:
我们这样分解:
Team A:
- Views
- CSS
- JavaScript
Team B:
- Controllers
- Models
- Database
We use Mind Mapping applications to work out what Controllers and Views we need first, so the whole team knows how to tie things together.
我们使用Mind Mapping应用程序来确定我们首先需要的控制器和视图,因此整个团队知道如何将事物联系在一起。
It's worked brilliantly for us, increased our productivity substantionally.
它对我们来说非常出色,大大提高了我们的生产力。
#3
1
By use case or task. Helps spread the knowledge about the entire process around.
通过用例或任务。帮助传播有关整个过程的知识。