This book could be useful as well. We plan on buying it next week ourselves.
http://www.amazon.com/Communicating-Design-Developing-Documentation-Planning /dp/0321392353/ref=cm_taf_title_featured?ie=UTF8&tag=tellafriend-20 -- Regards, Tony Chester | Web Director OnWired Next Generation Web Solutions Local Number: 919.647.9403 Mobile: 919.434.6651 FAX: 630.214.0810 Email: [EMAIL PROTECTED] Web: www.OnWired.net On 4/8/07 8:18 PM, "wsg@webstandardsgroup.org" <wsg@webstandardsgroup.org> wrote: > From: Lee Powell <[EMAIL PROTECTED]> > Date: Sat, 7 Apr 2007 15:28:53 +0100 > Subject: Client Side Development Process > > Hi all > > I wonder if anyone can offer some advice. I've recently landed a new > development position within a very credible digital agency as part of > their client side development team. One of our things to do is > develop a rock solid development process we work through for every > project. Traditionally we don't get our hand dirty until a client > signs off what the design team have produced, however we are going to > try to change this and get involved from an earlier point in the > project. > > Would anyone like to offer any advice on setting up this process, and > any advice on things to take into consideration for inclusion of the > process. It'd be great to compile some documentation, and share it > with the rest of the community... > > We're starting from a blank canvas so any advice appreciated. > > Kind Regards > > Lee Powell > > > From: "Jermayn Parker" <[EMAIL PROTECTED]> > Date: Sun, 8 Apr 2007 08:42:17 +0800 > Subject: Re: [WSG] Client Side Development Process > > The best suggestion I can come up with is an ebook on grayscreen prototyping > > Hear are my thoughts etc about it: > http://germworks.net/blog/2007/03/28/clients-vs-developer-wars-review/ > > > > On 4/7/07, Lee Powell <[EMAIL PROTECTED]> wrote: >> > >> > Hi all >> > >> > I wonder if anyone can offer some advice. I've recently landed a new >> > development position within a very credible digital agency as part of >> > their client side development team. One of our things to do is >> > develop a rock solid development process we work through for every >> > project. Traditionally we don't get our hand dirty until a client >> > signs off what the design team have produced, however we are going to >> > try to change this and get involved from an earlier point in the >> > project. >> > >> > Would anyone like to offer any advice on setting up this process, and >> > any advice on things to take into consideration for inclusion of the >> > process. It'd be great to compile some documentation, and share it >> > with the rest of the community... >> > >> > We're starting from a blank canvas so any advice appreciated. >> > >> > Kind Regards >> > >> > Lee Powell >> > >> > >> > ******************************************************************* >> > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm >> > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm >> > Help: [EMAIL PROTECTED] >> > ******************************************************************* >> > >> > > ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
