Print Page | Close Window

Usability vs. Cost

Printed From: One Stop Testing
Category: Types Of Software Testing @ OneStopTesting
Forum Name: Usability & Accessibility Testing @ OneStopTesting
Forum Discription: Discuss All that is need to be known about Usability & Accessibility Software Testing and its Tools.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=1317
Printed Date: 27Nov2024 at 9:53pm


Topic: Usability vs. Cost
Posted By: Suparna
Subject: Usability vs. Cost
Date 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.


Print Page | Close Window