单个开发人员应该遵循多少流程?正规的流程是不是太多了? [英] How much process should a single developer follow? Is a formal process too much?
问题描述
由于我最后一道题写得不好，大部分答案都很好，但完全没有按照我想提出的问题进行，我把它删除了，重新做成了这个问题.
我是我自己项目的独立开发者，通常都是非常小的事情，但我有一些想法可能会变成 FOSS 项目.我相信文档(在不同程度上，取决于特定项目和最终用户)、源代码控制和项目管理(包括错误跟踪、时间管理等).但是，我不确定我应该遵循多少正式流程.>
也许仅在源代码控制下保留自述文件、相关的设计/需求文档和代码内注释就足够了.或者也许有一个适合单个开发人员遵循的敏捷过程.或者也许我应该为每个项目采用老式的瀑布模型.
如果我什至需要一个正式的流程，有哪些类型的流程可供独立开发人员使用或可以采用?
<小时>我意识到我正在做一些任务，比如文档和源代码控制.但是，我不确定问题的部分内容.作为单独的开发人员，我应该采用更敏捷的方法(如果是，敏捷的哪个分支" - XP?Scrum?RAD?)还是更传统的方法(瀑布式或螺旋式?)?
即使您不需要流程来促进团队成员之间的良好沟通，流程也可以帮助您弥补您不像自己那样超人的事实你以为你是 18 岁的时候 :) 你决定做的文书工作"的类型和数量取决于你自己的长处和短处.记性不好?每天写下你的设计和想法.看树好看，看不到森林?确保您对您的要求和设计格外小心.能看到森林但不适合树木吗?详细的任务列表、时间估计和频繁的交付是您的朋友.
归结为:您可能会搞砸什么，哪些流程有助于您的特定工作方式.
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.
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.
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?
EDIT: 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?)?
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屋！
