How do folks manage requirement(s) priority and value? i.e. how do you know if what you are gathering is truly worth building out?
It seems this is where many products fail. We build or design stuff that people don't need and we are evaluating the "usefulness" way too late in the project. The sweet spot seems to be helping a Product Manager identify if something should be built and a more effective use of resources as you iterate forward. Thoughts? rgds, Dan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=41112 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... disc...@ixda.org Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
