Everyone,
I am consulting on a project which has suffered some rollout problems, to
put it mildly. The primary contractor, who developed and tested the site
on one system then tried to roll it out on another, is claiming that this
is an acceptable practice. Needless to say, the rollout was a complete
failure and the business site has been completely down since.
I am working with the client to develop a response to this that the primary
contractor will listen to. The client would like the primary contractor to
take responsibility for the work still needing to be done, as opposed to
asking for more funding to "redevelop" the site on the new host.
Does anyone have references for Best Practices in developing sites, in
particular the business and procedural issues involved? My company is
developing some for this client, for future use. I am not finding anything
useful for the host/server side of development; most everything out there
relates to client and page development. My client needs the work done and
would like some outside references to bolster the assurances we have given
him regarding appropriate development procedures and accepted best practices.
Any suggestions?
Bruce Humphrey
____ The WDVL Discussion List from WDVL.COM ____
To Join wdvltalk, Send An Email To: mailto:[EMAIL PROTECTED] or
use the web interface http://e-newsletters.internet.com/discussionlists.html/
Send Your Posts To: [email protected]
To change subscription settings, add a password or view the web interface:
http://intm-dl.sparklist.com/read/?forum=wdvltalk
________________ http://www.wdvl.com _______________________
You are currently subscribed to wdvltalk as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016
Please include the email address which you have been contacted with.
