My quandary is that you mention "developers" in #3 and #16/18, and it seems the developers' input is more of a "let me know if we are doing something impossible, otherwise we'll just go along" type of feedback, and the coding starts after the design is finalized.
Developers can't always predict the technical issues that will come up, or whether something doesn't make sense. One way I've seen it done is to have the developers coding as soon as the wireframes are out; thus the programming follows an iterative process concurrently with the design. Any changes that are dependent upon each other will most likely surface at the same stage. And yes, I agree with Brian, your user stories should be done first, and should be based on research. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=45767 ________________________________________________________________ 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
