Which is a good Project Managment Method to Develop a Website? XP? The Waterfall Model?
+1
A:
Agile/XP would be best.
Waterfall would be the worst choice in my opinion.
Justin Niessner
2010-02-26 20:15:11
Thank you for the help, i will use XP for my projects
streetparade
2010-02-26 20:44:18
+1
A:
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.
Jeffrey Hines
2010-02-26 20:25:36
+2
A:
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/
klabranche
2010-02-26 20:33:06
-1 for your "Anything but waterfall..." statement. Waterfall may be the best method if it is what fits the needs of the client.
Jeffrey Hines
2010-02-26 20:41:18
Good point Jeffrey. Perhaps a little to absolute. However, I think you can give the client what they want without following waterfall yourself even if they are used to that.
klabranche
2010-02-26 21:19:53
+1
A:
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.
Mutant
2010-02-27 06:39:19
A:
Use waterfall! But:
- Set duration of the project to 1 month.
- Then repeat this project until customer is happy!
Max Kosyakov
2010-03-01 04:14:37
Hasan, I'm sorry you have such an experience. Can't say all of my customers are happy, but most of them are. Anyway, having customer unhappy has it's good sides: you are always employed and (provided you have negotiated the contract right) always have income.
Max Kosyakov
2010-03-01 10:52:42
+1
A:
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.
Chris Perkins
2010-03-01 04:57:25
I'm not sure that I agree with your distinction between site to me, they are both applications of varying scopes. But +1 for your 1st paragraph.
Joe Internet
2010-03-01 05:34:40