|Project Management for websites !!|
Which one is best ?
| 9:05 pm on Jun 26, 2002 (gmt 0)|
Which is the best way to handle a web site project ?.
I use spiral and waterfall methods,
has anybody tried any new methods ?
| 9:16 pm on Jun 26, 2002 (gmt 0)|
Not familiar with the terminology, do you mind explaining the spiral and waterfall methods?
| 9:39 pm on Jun 26, 2002 (gmt 0)|
ok i will explain briefly ,
and so on,
in this method step1 is the place where you ask clients regarding their requirements, in the step2 you plan it (pert/cpm) and give the client an approximate cost ... thus you design your own steps for the remaining , if one step fails you go to the previous step but not before that.
While in spiral method...oops i cannot draw and show it to you here,
Consider a circular spiral , the steps are rotating, you complete all the steps at one go , just complete the project and show it to client( the final output). then when the client tells his views like he wanted one more feature etc etc you develop more more version so spiral model always continues and goes on and on ... this is mostly used ...... ( remeber windows 3.1 ..---> windows xp ) ?
Nowadays corporates invent their own models and strategies against the competators ,
So if anybody having any ideas of new models ? WELCOME..
| 4:37 pm on Jun 28, 2002 (gmt 0)|
OK, thanks for the explantion.
In my limited experience with full projects for anyone other than myself, here is my approach. Understand the industry the client is in
Listen to the client's desires
Understand how the internet can help their business
Tell them what they should desire
Agree on project and price
Work out any ongoing needs, maintenance options
I guess that is the step (waterfall) method.
The book, Secrets of Successful Websites: Project Management on the World Wide Web demonstrates successful and failed project management methods.
| 7:38 am on Jul 2, 2002 (gmt 0)|
I would use a mix of step and spiral. Basically the steps mentioned by JamesR are the right ones, thou they might be a bit more detailled for practical use. What you need to do for each of these steps is APIR:
- Analysis (of the requirements)
- Planning (how to realise, with what tools/methods)
- Implementation (that's the point when you actually DO something)
- Review (with your client, boss, whatever, to check whether everyone agrees on this steps results before going on)