Becky

Unregistered less info
78 reputation
3
bio website
location
age
visits member for 3 years, 8 months
seen Dec 22 '10 at 17:07

Nov
22
comment How do you communicate severity of design bugs? Do you have any standardized ways of doing it?
Hey Thom - Not sure I'm following you at all here. We do have all these interfaces implemented, after which we've discovered usability problems. We never have funding to fix all the usability problems but we do have explicit funding to fix any kind of functional bugs. So this proliferates known usability issues, however they are identified, in software that meets its specific functionaly requirements but is hard to use. We need a better way of sorting through all the usability problems that are left over.
Nov
18
comment An icon indicating something has changed or been edited?
yeah, an exclamation point in a yellow triangle or alone might be nice - that's pretty universal. it doesn't really say change but it calls attention.
Nov
18
awarded  Scholar
Nov
18
accepted How do you communicate severity of design bugs? Do you have any standardized ways of doing it?
Nov
18
comment How do you communicate severity of design bugs? Do you have any standardized ways of doing it?
thanks mark! nice approach, i'm happy for you! we don't have an agile process; we have an unusual development situation. We've been pushing for more funding for usability but it's true, people often want more stuff rather than better. Also some teams given some free reign to make usability improvements have done a poor job of utilizing their budgets - so that doesn't help!! Partially I think this is because they had difficulty understanding which bugs were most important. We actually have many usability-oriented developers, however, so making improvements within dev teams is possible! thanks.
Nov
18
comment How do you communicate severity of design bugs? Do you have any standardized ways of doing it?
I should point out that I'm not trying to make the usability bugs more severe or more important than functional bugs. I'm trying to integrate them with the process while using it to communicate clearly amongst widely distributed teams. We have a lot more usability bugs than functional bugs, however, and many developers that care about usability - we just want words for communicating in a clear language about the issues we have.
Nov
18
comment How do you communicate severity of design bugs? Do you have any standardized ways of doing it?
You can figure out some usability problems without testing. But that's not the point. Some usability problems cause users to be unable to use any of the functionality that was developed, or they will refuse to. If you have competition, users can choose the competitor instead. So less functionality that can actually be easily used can make a lot more $ than more functionality that you can't figure out (because in your mind it is not more functionality). Besides, your comment isn't even true of programming - things can work poorly or be hard to maintain, it's not just work or doesn't.
Nov
18
comment How do you communicate severity of design bugs? Do you have any standardized ways of doing it?
Hey there - we are not in an agile setting exactly, we do agile iterations, sometimes referred to a spiral, but we are a very large team making some pretty complex software. there are lots of triages and designers always attend and weigh in. We are incorporating lots of descriptions, storys and screens, but we are dealing with large numbers of bugs and don't always have the time to give each what they need.
Nov
18
comment How do you communicate severity of design bugs? Do you have any standardized ways of doing it?
That is an excellent article! Thank you so much, that was exactly the kind of thing I was looking for!!
Nov
18
awarded  Student
Nov
17
awarded  Teacher
Nov
17
answered An icon indicating something has changed or been edited?
Nov
17
asked How do you communicate severity of design bugs? Do you have any standardized ways of doing it?