|chapambrose on 19 Nov 2007 16:38:52 -0000|
As an interaction designer I was taught to research and understand the context of where your software is going to live, design the interface and test it with real users--refining it till it's as good as it can be; then pass it over to the programmers.
I learned you waste money when you start coding before you design. "Why hire programmers to code something you're not going to use, when you can just mock it up in photoshop instead?"
I'm not sure I agree with all that, but I find myself doing more and more coding with ruby on rails and taking on entire projects from start to finish. I'm interested in how I can use the Agile mantra to improve my process (but I'm still weary of writing any code until you've designed it all, it just seems like you'd be too attached to throw away something that's not working or unnecessary).
Also curious how agile works in a one/two man shop.
I'm a developer(pseudo) because I'm a designer who has no friends who can code.
On Nov 19, 2007, at 11:20 AM, David Bogus wrote:
I'm doing the agile talk and I'd like it to be well received and helpful so if you have a minute, I like you to use it to help me understand what I should focus my talk on.