7 replies
by jooehrlein
If you're looking for a timeline listing # days for development, # days for testing, etc., I don't think you'll find one. That will vary with the features you implement, as well as the strength and size of your staff.
If you're looking for a workbreak down structure listing tasks to be performed, then I don't think a web project is very different than any other software project. The emphasis may be on slightly different things, but the same types of tasks apply.
One lightweight process is Extreme Programming. Check out http://www.extremeprogramming.org for their explanation of how they organize their projects.
The people who brought you UML have defined the Unified Process. There are several books available on it. The primary oneis available at http://www.amazon.com/exec/obidos/ASIN/0201571692/qid=986999434/sr=1-4/ref=sc_b_5/102-2448016-2832154. Rational also has a slightly tweaked version of this called the Rational Unified Process (see http://www.rational.com/products/rup/index.jsp).
by dr
by realgem
I agree with the above. However, here are the basic milestones that you will probably have:
Approve Requirements
Approve Solution Architecture
Acquire Hardware / Software
Complete Development
Complete Testing
Complete Rollout
Of course, you would repeat this for every requirement set that you want to deliver...you don't have to do it all at once.
by dr
by the chad
Don't forget Training and Documentation. If you don't document the system, future folks won't understand what you did, or your motivation behind why you did it -- and might end up reinventing the wheel / making the same mistakes you already learnedfrom.
Training will help your support staff keep the system running / service clients.
by dr
by dr
This discussion is closed to new replies.
Trending IT Employment posts
Sort by Trending