一个单一的开发人员应该有多少的过程遵循？是一个正式的程序太多了？ [英] How much process should a single developer follow? Is a formal process too much?
问题描述
由于我没有做好编写最后一个问题，而问题的答案是好的，但不是所有在我打算这个问题去的方向，我删除了它，并重塑其作为这个问题
Since I didn't do a good job writing the last question, and most of the answers were good, but not at all in the direction I intended for the question to go in, I deleted it and remade it as this question.
我对我自己的项目，一般都非常小东西一个单独的开发者，但我有可能会变成FOSS项目的一些想法。我相信，在文件（在不同程度上，取决于具体的项目和最终用户），源代码控制和项目管理（包括缺陷跟踪，时间管理，等等）。但是，我不知道href=\"http://en.wikipedia.org/wiki/Software_development_process\"多少
I'm a solo developer on my own projects, generally very small things, but I have a few ideas that might turn into FOSS projects. I believe in documentation (to varying degrees, depending on the specific project and the end user), source control, and project management (including bug tracking, time management, and so on). However, I'm not sure how much of a formal process I should be following.
也许只是死死的README文件，相关的设计/需求文档和源代码控制下IN- code注释就足够了。或者，也许有一个敏捷过程适合于单个开发人员跟随。或者，也许我应该对每个项目一个老派的瀑布模型。
Perhaps just keeping a README, associated design/requirements documents, and in-code comments under source control is sufficient. Or maybe there's an agile process that is suitable for a single developer to follow. Or maybe I should take an old-school waterfall model for each project.
可以采用独唱开发商有什么样的进程，或者，如果我甚至需要一个正式的流程？
What kinds of processes exist for or can be adopted to a solo developer, if I even need a formal process?
编辑：我知道有一些我做的是做像文档和源代码控制任务。不过，我不知道这个问题该怎么一部分。作为一个单独的开发者，我应该采取更灵活的方式（如果是这样，它敏捷分支 - ？？？XP Scrum的RAD）？或者更传统的方法（？瀑布或螺旋）
I realize that there are tasks that I'm doing to be doing like documentation and source control. However, I'm not sure about the how part of the question. As a solo developer, should I adopt a more agile approach (if so, which "branch" of Agile - XP? Scrum? RAD?) or a more conventional approach (waterfall or spiral?)?
推荐答案
即使你不需要进程，促进团队成员之间良好的沟通，过程可以帮你弥补的事实，你是不是像你一样超人还以为你当你是18 :)你决定做'文书'的类型和数量取决于你自己的长处和短处。记性不好？每天写下你的设计和想法。好看到树木，不见森林？确保您格外小心你的要求和设计。看到好森林，但没有树？详细的任务列表，时间估计，以及频繁的交付是你的朋友。
Even if you don't need process to promote good communication between team members, process can help you compensate for the fact that you aren't as superhuman as you thought you were when you were 18 :) The type and amount of 'paperwork' you decide to do depends on your own strengths and weaknesses. Bad memory? Write down your designs and thoughts daily. Good seeing trees but not forests? Make sure you are extra careful with your requirements and designs. Good seeing forests but not trees? Detailed task lists, time estimates, and frequent deliverables are your friend.
它归结为：你是什么可能会陷入困境，以及处理与帮助工作的特定方式。
It boils down to: what are you likely to mess up, and which processes help with your particular way of working.
这篇关于一个单一的开发人员应该有多少的过程遵循？是一个正式的程序太多了？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
