Skip to main content
Software Quality Assurance & Testing

Return to Answer

deleted 1 characters in body
Source Link
SLoret
SLoret
  • 191
  • 4

For me it's easy.

Happy Customers (ie low production support) = High Software Quality

Unhappy Customers (ie lostslots of production support) = Low Software Quality

Also, talking to the team. As one of the other posts stated, not all bugs are equal in magnitude. Encourage your testers to speak up when the quality is going down the drain. They should know better than anyone or any metric.

For me it's easy.

Happy Customers (ie low production support) = High Software Quality

Unhappy Customers (ie losts of production support) = Low Software Quality

Also, talking to the team. As one of the other posts stated, not all bugs are equal in magnitude. Encourage your testers to speak up when the quality is going down the drain. They should know better than anyone or any metric.

For me it's easy.

Happy Customers (ie low production support) = High Software Quality

Unhappy Customers (ie lots of production support) = Low Software Quality

Also, talking to the team. As one of the other posts stated, not all bugs are equal in magnitude. Encourage your testers to speak up when the quality is going down the drain. They should know better than anyone or any metric.

Source Link
SLoret
SLoret
  • 191
  • 4

For me it's easy.

Happy Customers (ie low production support) = High Software Quality

Unhappy Customers (ie losts of production support) = Low Software Quality

Also, talking to the team. As one of the other posts stated, not all bugs are equal in magnitude. Encourage your testers to speak up when the quality is going down the drain. They should know better than anyone or any metric.