That’s expected behavior and Not a Bug


I keep hering the following phrases from our Development Team here

  1. That’s an expected behavior and Not a Bug
  2. That’s by Design

Today, I have an interesting debate with our Product Manager on a Issue. He put is as “That’s an Expected Behavior and Not a Bug”

I have been looking at root causes of these problems & why do run into this kind of debates always. The following limitations came

We could have avoided the same incase if

  1. Clarity on the Requirements across all the teams 
  2. Limitations of the Technology
  3. Usability Principles (UI Guidelines)

The above two arguments can be avoided if both teams have clarity on the above three.

Advertisements
Explore posts in the same categories: Bug Tracking, Software Development, Software Testing

3 Comments on “That’s expected behavior and Not a Bug”

  1. venkatreddyc Says:

    Hi Srini,

    Thanks for pointing me to this post in the first place. Your views are nice and i prefer this as one of the good approach to handle this kind of debates.

    But then, things may not be that smooth or simple in all the scenarios.

    I work for a product development company and most of the requirements will be captured by the Sales / Architecture / Management Team with some inputs from the Customers.

    Here the requirement is not specific to a customer and the big problem as i said earlier is the Clarity on the requirements itself.

    In product development, there will be different customers and see all these requirements won’t come in from them.

    As i said above in my post
    The root cause for most of the scenarios from my perspective are that

    1. Clarity on the requirements across the teams (Management / Sales / Arch / Dev / Testing)

    2. Attributing the Technical Limitations to the Requirements and not disclosing the same

    3. Not coming up with the required documents that will clarify the ambiguities

    4. Lack of understanding on how the Systems behave in general ( Take a step up and see how this should behave in the real time )

    5. Taking things personally instead of understanding the System


  2. […] That’s Expected Behavior & Not a Bug – Avoid conflicts over the issues raised. Don’t fight but capture the required information. […]


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: