 | | | |
Most development organizations track software bugs and their severity in a corporate database, which is shared with product development and tech support teams. We find, however, that these same organizations seldom have a standard method, if any, of tracking usability issues. Usability practitioners communicate usability problems through reports, highlight tapes, and formal briefings, but are these methods adequate for tracking usability problems through successive cycles of product development?
View all 4 works published by Interactions |
The Whiteboard: Tracking Usability Issues: To Bug or Not to Bug?
portal.acm.org/citation.cfm?id=369825.369828
Wilson, Chauncey E. and Kara P. Coyne
Interactions
2001
Abstract: Most development organizations track software bugs and their severity in a corporate database, which is shared with product development and tech support teams. We find, however, that these same organizations seldom have a standard method, if any, of tracking usability issues. Usability practitioners communicate usability problems through reports, highlight tapes, and formal briefings, but are these methods adequate for tracking usability problems through successive cycles of product development?
|
|
| |
There are 16 readers currently online: 2 registered users and 14 guests. Register.