Deepak

• Jun 8th, 2005

 

QA has to look over all the Possibilities like Assessment, Bug Fixes,Product Quality,Client Interaction and Overall Development of Imparting Tasks for Testers.

choudary

• Jul 5th, 2005

 

Quality Assurance group assure the Quality it must monitor the whole development process. they are most concentration on prevention of bugs.  
 
it must set standards, introduce review procedures, and educate people into better ways to design and develop products.

Sangeetha.K

• Aug 16th, 2005

 

Let's say an engineer is hired for a small software company's QA role, and there is no QA team. should he take responsibility to set up a QA infrastucture/process, testing and quality of the entire product? No, because taking this responsibility is a classic trap that QA people get caught in. Why? Because we QA engineers cannot assure quality. And because QA departments cannot create quality. What we can do is to detect lack of quality, and prevent low-quality products from going out the door. What is the solution? We need to drop the QA label, and tell the developers, they are responsible for the quality of their own work. The problem is, sometimes, as soon as the developers learn that there is a test department, they will slack off on their testing. We need to offer to help with quality assessment only.

Venkat

• Aug 25th, 2005

 

QA is responsible for the Preventive action. That's QA is necessary right from the requirement gathering phase. QA engineer needs to set a goal for each and every statge of the project life cycle and make sure the development team achieves the plan. If not conduct causal analysis meeting to find out the problem and errodicate in the upcoming phases.

unna

• Jul 11th, 2006

 

Hi,

      What is the role of QA in improving standards?

Regards

Unna

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 29th, 2009

 

The role of Quality Assurance (QA) in a software development project includes:

1) Study past releases to isolate causes of process inefficiencies and ineffectiveness
2) This includes studying past releases to isolate causes of defects
3) Establish key metrics that help identify causes of poor quality
4) Establish a means to measure them
5) Monitor problem areas based on applied metrics
6) Capture data
7) Compile the results
8) Report your findings
9) Plan improvements with key stakeholders
10) Implement the improvements
11) Monitor areas after improvements are installed
12) Capture data
13) Compile the results
14) Report your findings
15) Determine whether any adjustments are needed with key stakeholders
16) Return to step [10] until processes are under control
17) Return to step [1]