超轻软件开发流程
到目前为止，我参与的开发过程中，大多数团队都是由单一成员组成，有时甚至是两个成员。
我们主要使用python + django进行开发，开发过程实际上非常快，并且我们确实有代码审查，设计模式讨论和不断的重构。
尽管团队规模很小，但我确实认为有一些可以强制执行的开发流程/最佳实践。例如，使用 svn 肯定比常规的副本备份更好。
我确实读过一些文章&关于敏捷、XP 和敏捷的书籍持续集成，我认为它们很好，但对于这种情况来说仍然太重（1 或 2 人的团队，以及快速编码）。例如，恕我直言，具有良好的设计模式和迭代开发+重构，TDD可能是一种矫枉过正，或者至少开销并没有超过其优点。结对编程也是如此。自动化测试是一个好主意，但在技术上似乎并不是每个项目都可行。
我们目前的做法是：
svn+milestone+codereview
不知道是否有专门针对这样的超轻团队的开发流程/最佳实践？
For the development process I have involved so far, most have teams of SINGLE member, or occasionally two.
We used python + django for the major development, the development process is actually very fast, and we do have code reviews, design pattern discussions, and constant refactoring.
Though team size is small, I do think there are some development processes / best practices that could be enforced. For example, using svn would be definitely better than regular copy backup.
I did read some articles & books about Agile, XP & continuous integration, I think they are nice, but still too heavy for this case (team of 1 or 2, and fast coding). For example, IMHO, with nice design pattern, and iterative development + refactoring, the TDD MIGHT be an overkill, or at least the overhead does not out-weight the advantages. And so is the pair programming. The automated testing is a nice idea, but it seems not technically feasible for every project.
our current practices are:
svn + milestone + code review
I wonder if there are development processes / best practices specifically targeted on such super light teams?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您希望同时拥有源代码控制，以便可以撤消您现在后悔的更改，以及将变更集与故事、工作项或请求或您在工作流程中所说的任何内容建立某种连接。随着时间的推移，这将让您回答为什么对代码进行特定更改，或探索特定决策所需的代码更改。像这样的探索将帮助你在未来做出更好的决定。您可能还需要管理您的待办事项/待办事项列表/客户请求/绝妙想法，如果这直接连接到您的源代码控制，那就更好了。
You want to have both source control, so you can undo changes you now regret, and some sort of connection of changesets to stories or work items or requests or whatever you call them in your workflow. Over time this will let you answer why you made a particular change to code, or explore the code changes that were required by a particular decision. Explorations like this will help you to make better decisions in the future. You probably also need to manage your backlog / todo list / customer requests / brilliant ideas and if that connects directly into your source control, so much the better.