Hi Jonathan, A good methodology should allow you to be as heavy or lite as the project requires. I work as an in-house IxD with a team of developers in Los Angeles and India. The developers use Agile methods that overlap rather nicely with my process, which is the Goal-Directed Design methodology created by the folks at Cooper. You might like Goal-Directed Design for identifingy how the design team works with project management, developers, and stakeholders. And it offers a good guideline for selecting and structuring tools/deliverables.
Depending on the schedule and resources, the thing that changes the most from project to project is the level of polish we put on artifacts and documentation. For example, on a large project with a reasonable schedule I'll create a lovely user & domain analysis document to provide context to stakeholders & developers. It summarizes our research, introduces the personas, and provides a nice narrative for each persona's scenarios. When there's no time to make a nice document out of all of this, we still do quick and dirty research but it stays on note pads, and white boards rather than getting compiled in a document. Then we'll just hold a meeting to share our research conclusions and introduce the personas. So in one project, the research phase may take months but if we're pressed for time it gets squeezed into days. Hope this helps :-) Angel Anderson ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
