Active Topics Memberlist Calendar Search Help | |
Register Login |
One Stop Testing Forum : Types Of Software Testing @ OneStopTesting : Usability & Accessibility Testing @ OneStopTesting |
Topic: Usability vs. Cost |
|
Author | Message |
Suparna
Groupie Joined: 28Apr2007 Online Status: Offline Posts: 72 |
Topic: Usability vs. Cost Posted: 14May2007 at 5:54am |
I've had a some issues come up where I thought it'd be a good idea to
make a change to the application to remove a situation that may be
"confusing" to the user.
A couple of these issues aren't getting done because other things take priority. Ok, I get that. I was also told that I should start thinking in terms of the amount of time involved in a mod and if I'd be willing to pay for something if the thing/widget/whatever works. Not that I think I'd be charged for a usability modification, but to think in terms of costs and such. So where do you draw the line? Where's the balance between submitting usability issues based on worth and leaving them out? I'm inclined to document them all and if the project mnager wants to lower their priority or set them to a "pending" status, at least they'll be documented. Post Resume: Click here to Upload your Resume & Apply for Jobs |
|
IP Logged | |
Forum Jump |
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
© Vyom Technosoft Pvt. Ltd. All Rights Reserved.