It depends on who the customer is. If you are your own customer, then definately Agile.
If your aren't your own customer then you will have to negotiate with your customer on your development method. If your customer wants a fixed bid project and a hard deadline, then you will be best served by the waterfall method.
If your customer is willing to be an active participant in the development process and doesn't have a hard deadline and fixed budget then you could do Agile/XP.
It always depends on the type of the website you are developing, how many developers you got, what is the timeline, expectation for delivery time. But definitely Agile or prototype-iterative method will work fine for website development. To complete the development in different phases, and enhancing in the chucks, as an when identifying the strong and weak areas.
As well you can check the factors like target audience, maximum used sectors of the site and prioritize the development of those pieces first.
Always consider to go with standard framework, that will make life easier in long run with the future developments.
I find that waterfall fits some web site projects fairly well. Get the requirements, wireframe a design, do the graphic design, convert the graphic designs to HTML/CSS/JS, then fill out the content of the site. Client signs off at each stage. If the site is large the last stage ("fill out content") is probably more work than all the preceding ones and you'll want to use iterative methodologies for it, not waterfall.
Waterfall tends to not fit web applications very well. Those are software, treat them as such.
发布评论
评论（6）
除了瀑布之外的任何东西......
但请记住，说你敏捷和真正敏捷是两件不同的事情。
为了使敏捷真正能够长期发挥作用，我们还必须做好几项技术工作。
http: //ayende.com/Blog/archive/2010/02/20/nice-process-but-what-about-the-engineering-bits.aspx
http://davybrion.com/blog/2010/02/youll-never-get-sustainable-免费进度/
Anything but waterfall....
But keep in mind that saying you are agile and being really agile are two different things.
For agile to really work over an extended period one has to also be doing several technical things well.
http://ayende.com/Blog/archive/2010/02/20/nice-process-but-what-about-the-engineering-bits.aspx
http://davybrion.com/blog/2010/02/youll-never-get-sustainable-progress-for-free/
敏捷/XP 是最好的。
在我看来，瀑布是最糟糕的选择。
Agile/XP would be best.
Waterfall would be the worst choice in my opinion.
这取决于客户是谁。如果您是自己的客户，那么肯定是敏捷。
如果您不是自己的客户，那么您将必须与客户就您的开发方法进行协商。如果您的客户想要一个固定的投标项目和严格的截止日期，那么瀑布法将为您提供最好的服务。
如果您的客户愿意积极参与开发过程，并且没有严格的截止日期和固定预算，那么您可以采用敏捷/XP。
It depends on who the customer is. If you are your own customer, then definately Agile.
If your aren't your own customer then you will have to negotiate with your customer on your development method. If your customer wants a fixed bid project and a hard deadline, then you will be best served by the waterfall method.
If your customer is willing to be an active participant in the development process and doesn't have a hard deadline and fixed budget then you could do Agile/XP.
这始终取决于您正在开发的网站的类型、您有多少开发人员、时间表、预期的交付时间。但敏捷或原型迭代方法绝对适合网站开发。完成不同阶段的开发，并在卡盘上进行强化，作为识别强项和弱项的依据。
您还可以检查目标受众、网站的最大使用区域等因素，并首先优先考虑这些部分的开发。
始终考虑采用标准框架，从长远来看，随着未来的发展，这将使生活变得更轻松。
It always depends on the type of the website you are developing, how many developers you got, what is the timeline, expectation for delivery time. But definitely Agile or prototype-iterative method will work fine for website development. To complete the development in different phases, and enhancing in the chucks, as an when identifying the strong and weak areas.
As well you can check the factors like target audience, maximum used sectors of the site and prioritize the development of those pieces first.
Always consider to go with standard framework, that will make life easier in long run with the future developments.
我发现瀑布非常适合一些网站项目。获取需求，对设计进行线框设计，进行图形设计，将图形设计转换为 HTML/CSS/JS，然后填写网站内容。客户在每个阶段签字。如果网站很大，最后一个阶段（“填写内容”）可能比前面的所有阶段都需要更多工作，您将需要使用迭代方法，而不是瀑布式。
瀑布往往不太适合网络应用程序。这些都是软件，就这样对待它们。
I find that waterfall fits some web site projects fairly well. Get the requirements, wireframe a design, do the graphic design, convert the graphic designs to HTML/CSS/JS, then fill out the content of the site. Client signs off at each stage. If the site is large the last stage ("fill out content") is probably more work than all the preceding ones and you'll want to use iterative methodologies for it, not waterfall.
Waterfall tends to not fit web applications very well. Those are software, treat them as such.
使用瀑布！但是：
Use waterfall! But: