My first job out of college was teaching software applications like MS Access, FoxPro, and Act!. Back then, in the late 90's, demand for these types of classes was much higher than it is today. This, I believe, is because today's software users are more sophisticated. Most have already been exposed to some flavor of word processing, spreadsheet, or email applications. Many can even teach themselves software or look online for answers.

After accepting the above, it's not too great a leap to also accept that modern software users are aware that software is not perfect. They have experienced application hangs and strange system errors and many users learn to avoid these bugs or recover via a reboot or similar.

If the above is true, why can't all bug lists be public? The culture of my dev team prefers to keep the bug list hidden because they believe users will have trust issues if we admit to known production bugs. I disagree. In fact, if properly facilitated, I think a public bug list can actually build user trust. Users are smart enough to see the value in having their software earlier, even at the expense of known bugs.

What do you think?


  1. Anonymous said...

    I think our users aren't too bright, and would mistake common bugs that can be fixed with an unstable product, if a product is indeed stable but we have 1-200 bugs that are mostly low priority, it sends the wrong message to our users.

  2. Anonymous said...


    One reason for keeping bug lists private might be fear of litigation/lawsuit from end users? I'm not sure how the law works in respect to that.

    I also agree with what desertfox mentioned.


  3. Anonymous said...

    I have to disagree with desertfox and Adam and agree with Eric.
    I believe it's better for users to know that Dev are aware of the bugs and in turn working on resolving them.
    Take for example the scenario that desertfox mentioned, if there are 1-200 low priority bugs then users are going to notice them and wonder why they weren't discovered by Dev/Test and this will cause mistrust and lose of confidence, if Dev is upfront and say 'Yes we are aware of these and they will get fixed and if you notice anything else please let us know and we'll sort those out too' it builds a good relationship.

    As for what Adam has mentioned surely a bug which could lead to a lawsuit is exactly what you need to let the world know about?!
    Not letting users know is what would lead to the lawsuit. If they are aware then the responsibility is with them.

  4. Anonymous said...

    Are you advocating the bug lists be made available to only the users of the application or the public (whether or not a member of the public is a user of the application)?

    I think that once Development and Testing are finished with their work and the application has been deployed/ distributed to the users, selected known bugs can be provided for viewing by the users.

    Making all known bugs visible to each user might de-motivate a user (especially if the number of bugs is large). It can give rise to unrealistic expectations (a user might expect prompt resolution of any bug while being unaware of the constraints being faced by the development team).

  5. Eric Jacobson said...

    Inder P Singh,

    Great question. It forces us to think about a variety of software types (e.g., shrink-wrap vs. custom).

    I think the bug list should be available to the general public whether they have a login or not. Again, I believe it shows more integrity for the app to make the bug list public, even in an extreme case where there may be 1000 open bugs.

    Look, if the stakeholders decide to go live with 1000 bugs, they obviously assume there is enough working functionality to provide value to someone who matters. The quality of the software will speak for itself.

    I think as years go by, more users will agree with me.

  6. Tony Bruce said...

    Eric, I posted a link to this post on sqaforums:

    Thought you might be interested in reading the responses.

Copyright 2006| Blogger Templates by GeckoandFly modified and converted to Blogger Beta by Blogcrowds.
No part of the content or the blog may be reproduced without prior written permission.