DCSIMG
What Influences the Product's Quality? - SRL Group

SRL Group

This blog is about Team System, QA and Development methodologies and more...

VSTS Resources

Team System Bloggers

What Influences the Product's Quality?

A few days ago I went to a customer of mine that wants to produce a higher quality products.

The main candidate for the modification was the QA group because the QA group is responsible for the quality in the development process.

After a short investigation it was shown that not only the QA team should be modified but all the "players" that take part in the development process of the products should be a part of the change.

Some of the conclusion were:

  1. better requirements should be written so that the QA will have its main input for the quality process.
  2. A change management process should be established so all changes made after the planning phase will be properly checked for there influence on the development process.
  3. Unit tests should be written by the developers.
  4. Bugs should have a proper work flow not only inside the QA team but thru all the bug's lifecycle.

These are not all the conclusions from our investigation, but it can show that changes should be made thru all the application lifecycle in order to get a better quality.

It is a common mistake to blame the QA for a poor quality of a product, I don't say that this is not the case the QA team has the biggest influence on the quality, what I say is that a more comprehensive investigation should be made in order to see what the problem really is before we put the blame...

Comments

Alex Odintsov said:

Many companies have the same issue and everybody is looking for a perfect solution. It looks like VS 2010 will give us much more than any other tool, but it wont fix "human" factor, i.e. people are still the main source for requirements and requirements are as good as person or a team who writes them.

That brings a question:

What defines "perfect requirements"?

If it does not exist, what kind of detail level is acceptable?

How much time developers or team leads should spent on getting more details about what they need to develop? How many details QA needs to be bale to create test cases based on provided requirements?

I know there are a lot of articles written, but if possible, I'd like to know your opinion.

# October 24, 2008 8:57 AM
Leave a Comment

(required) 

(required) 

(optional)

(required) 


Enter the numbers above: