You want to use Rational Unified Process in a one-person team? While I suppose it might be a hint about the sorts of things that you're going to have to do, it would seem to me to be an absurdly heavyweight thing to use formally. Like using a thermonuclear weapon to kill a mosquito, it will work but is still Doing It Wrong.
For a single person team, test-driven development is almost certainly a better choice, as it helps you focus on being immediately productive (and hence on staying motivated, the big long-term problem). You don't need a great deal more than that because you don't have to worry about problems like lack of communication between development teams…
I think it might be reasonable if you cannot estabilish a team for trying out a process. But practically, you would certainly want to adjust it to remove artifacts, which are used for communication, which you will not need. You should also bear in mind, that it might be hard to act objectively especially in testing and all other review activities.
发布评论
评论（3）
您想在一个人团队中使用 Rational Unified Process 吗？虽然我认为这可能是对你必须要做的事情的暗示，但在我看来，正式使用它是一个荒谬的重量级的东西。就像用热核武器杀死蚊子一样，它会起作用，但仍然是做错了。
对于单人团队来说，测试驱动开发几乎肯定是更好的选择，因为它可以帮助你专注于立即提高工作效率（从而保持动力，这是一个长期的大问题）。您不需要更多的东西，因为您不必担心诸如开发团队之间缺乏沟通之类的问题......
You want to use Rational Unified Process in a one-person team? While I suppose it might be a hint about the sorts of things that you're going to have to do, it would seem to me to be an absurdly heavyweight thing to use formally. Like using a thermonuclear weapon to kill a mosquito, it will work but is still Doing It Wrong.
For a single person team, test-driven development is almost certainly a better choice, as it helps you focus on being immediately productive (and hence on staying motivated, the big long-term problem). You don't need a great deal more than that because you don't have to worry about problems like lack of communication between development teams…
我认为如果你不能建立一个团队来尝试一个流程，这可能是合理的。但实际上，您肯定希望对其进行调整以删除用于通信的工件，而您将不需要这些工件。您还应该记住，可能很难客观地采取行动，尤其是在测试和所有其他审核活动中。
I think it might be reasonable if you cannot estabilish a team for trying out a process. But practically, you would certainly want to adjust it to remove artifacts, which are used for communication, which you will not need. You should also bear in mind, that it might be hard to act objectively especially in testing and all other review activities.
是的，您可以在“一个”人项目中使用 RUP...:-)
看一下：
Kruchten，“一个团队的软件开发过程”
在线阅读：http://www.ibm.com/developerworks/rational/library/内容/RationalEdge/feb02/ProcessForOneFeb02.pdf
Yea, you can use RUP in "one" man project...:-)
Just look at it:
Kruchten, "A Software Development Process for a Team of One"
Read Online at : http://www.ibm.com/developerworks/rational/library/content/RationalEdge/feb02/ProcessForOneFeb02.pdf