The process I've used that was most successful was to track the issues/changes in our bug tracking system. We tried various versions of this where we tracked the issues/changes individually but that was too much, screen by screen which worked out pretty well, or in one instance, with everything in there. We also affinitized issues and entered them that way which worked the best. We did this as a team--the developers, Business Analysts, usability, stakeholders so there was complete buy-in as to what needed changed and why.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=35763 ________________________________________________________________ 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
