如果您要收费（或者不想永远陷入该项目），项目计划总是一个好主意。即使它只是一个一页概述网站将有什么（有多少页，任何特殊功能）以及谁负责什么。您应该考虑到您将花费 20% 的时间（或过去经验告诉您的任何百分比）用于文档或非编码类型的工作，您可以更好地估计所需的工作量。如果是朋友，您可能想告诉他们前 X 小时免费，但之后您的费率是每小时 Y 美元。另外，准确记录您所花费的时间，以便您可以向他们展示所付出的努力。此外，保留准确的日志可以帮助您估计未来的项目。
If you are going to be charging money (or don't want to be stuck doing the project forever), a project plan is always a good idea. Even if it's just a one-pager outlining what the web site will have (how many pages, any special features) and who is responsible for what. You should factor in that you'll spend 20% of your time (or whatever percentage past experience has taught you) on documentation or non-coding type work, you can give a better estimate of the effort needed. If it's a friend, you might want to tell them that you'll do the first X hours for free, but after that your rate is $Y per hour. Also, keep an accurate log of the time you've spent so that you can show them the amount of effort that is involved. Also, keeping an accurate log helps you estimate future projects.
A project that does not need a plan is a project that does not need to be even started. In my opinion everything needs a plan, what changes is the extent of that plan. A plan could be just a list of deliverables and some deadline attached to each one. A more robust plan should include time charts, cost, phases, communications howto, dependencies, etc. So I think everything needs a plan, the contents of the plan is what changes depending on the project complexity.
In preparing for battle I have always found that plans are useless, but planning is indispensable.
It seems the same in many software projects: you'll find that your plans need to be continually updated and that your first plan was quite different from what you finally completed. But that's okay, it's much better to put some planning in up front than to try something by the seat of your pants.
Agilists try to accommodate such changes in plans by breaking longer term plans into small "sprints" of 2-4 weeks. They'll have more details on the near term sprints, and fewer details on the longer term goals.
You'll especially want to be more detailed and precise if the project is bigger, if you are doing this for an external customer, or if you're attempting something new for you. It's less important (though not unimportant) for smaller projects and types of work you've done before and are very familiar with.
发布评论
评论（4）
如果您要收费（或者不想永远陷入该项目），项目计划总是一个好主意。即使它只是一个一页概述网站将有什么（有多少页，任何特殊功能）以及谁负责什么。您应该考虑到您将花费 20% 的时间（或过去经验告诉您的任何百分比）用于文档或非编码类型的工作，您可以更好地估计所需的工作量。如果是朋友，您可能想告诉他们前 X 小时免费，但之后您的费率是每小时 Y 美元。另外，准确记录您所花费的时间，以便您可以向他们展示所付出的努力。此外，保留准确的日志可以帮助您估计未来的项目。
If you are going to be charging money (or don't want to be stuck doing the project forever), a project plan is always a good idea. Even if it's just a one-pager outlining what the web site will have (how many pages, any special features) and who is responsible for what. You should factor in that you'll spend 20% of your time (or whatever percentage past experience has taught you) on documentation or non-coding type work, you can give a better estimate of the effort needed. If it's a friend, you might want to tell them that you'll do the first X hours for free, but after that your rate is $Y per hour. Also, keep an accurate log of the time you've spent so that you can show them the amount of effort that is involved. Also, keeping an accurate log helps you estimate future projects.
正如您可能已经发现的那样，没有一个项目太小而不能至少有一个非正式的书面计划。即使它只是一个功能列表。
As you may have already figured out, no project is too small to have at least an informal, written plan. Even if it's just a features list.
不需要计划的项目甚至不需要开始。在我看来，一切都需要计划，改变的是计划的范围。计划可以只是可交付成果的列表以及每个交付成果所附的截止日期。一个更健全的计划应该包括时间表、成本、阶段、沟通指南、依赖关系等。所以我认为一切都需要一个计划，计划的内容是根据项目的复杂程度而变化的。
A project that does not need a plan is a project that does not need to be even started. In my opinion everything needs a plan, what changes is the extent of that plan. A plan could be just a list of deliverables and some deadline attached to each one. A more robust plan should include time charts, cost, phases, communications howto, dependencies, etc. So I think everything needs a plan, the contents of the plan is what changes depending on the project complexity.
德怀特·艾森豪威尔谈规划：
在许多软件项目中似乎都是一样的：你会发现你的计划需要不断更新，并且你的第一个计划与你最终完成的计划有很大不同。不过没关系，提前做一些计划比凭感觉尝试要好得多。
敏捷主义者试图通过将长期计划分解为 2-4 周的小“冲刺”来适应计划中的此类变化。他们将提供有关近期冲刺的更多详细信息，以及有关长期目标的较少详细信息。
如果项目较大，如果您是为外部客户做这件事，或者如果您正在尝试为自己做一些新的事情，您会特别希望更加详细和精确。对于较小的项目和您以前做过且非常熟悉的工作类型来说，它不太重要（尽管并非不重要）。
Dwight Eisenhower on planning:
It seems the same in many software projects: you'll find that your plans need to be continually updated and that your first plan was quite different from what you finally completed. But that's okay, it's much better to put some planning in up front than to try something by the seat of your pants.
Agilists try to accommodate such changes in plans by breaking longer term plans into small "sprints" of 2-4 weeks. They'll have more details on the near term sprints, and fewer details on the longer term goals.
You'll especially want to be more detailed and precise if the project is bigger, if you are doing this for an external customer, or if you're attempting something new for you. It's less important (though not unimportant) for smaller projects and types of work you've done before and are very familiar with.