<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Wed, Sep 7, 2011 at 5:03 PM, Ed Lea <<a href="mailto:edleadesign@gmail.com">edleadesign@gmail.com</a>> wrote:<br>
> Unfortunately, development tends to lie further down the process than design<br>
> so any delays are often started at the concept/design/client approval end.<br>
> It's not to do with being a designer, it's to do with that stage of<br>
> development. Like any professional if a date is set and parameters fixed<br>
> then there is no reason a designer would deliver later than any other<br>
> profession.<br>
<br>
</div>I'm wondering if this implies a 'waterfall' methodology (because it<br>
sounds like it to me). If so, is that what's generally used to shape<br>
the way devs and designers interact?<br></blockquote><div><br></div><div>In my experience there has to be some agreement on concepts and features first and this is usually in the form of a mockup for the client/stake holder to approve. So by this point designers have already started making something. Tech side may already be involved, but not actually coded anything yet. So in 80% of projects I have worked on it is more of a 'waterfall' methodology.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
I thought the alternative would be some 'agile' approach. </blockquote><div><br></div><div>I don't see how a developer could start building something until the client/stake holder has signed off on functionality which is usually demonstrated in the form of wireframes+designs. </div>
<div><br></div><div>Of course, this is speaking from my design background - I couldn't comment on software projects where no visual design is required.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Getting back<br>
on topic, this would rely on good communication between devs and<br>
designers, and that might be easier if everyone was in-house...<br></blockquote><div><br></div><div>not necessarily. my current gig is working remotely for a company in germany. I've been doing that for 1.5 years. projects fly along because I'm never in a meeting unless I'm over there and communication through skype is short and to the point. I get the whole day to design with no interruptions :) but, like I said in previous email, build a relationship and the communication part will be much better.</div>
</div><br>