Create defect free software. Too many people (developers, PMs and Clients) that I have worked for as a consultant think that.
It doesn't matter how good your testing procedures are if there are no good procedures up to that point. I agree with those who have said that most defects are a result of poor communication, I've got the numbers to prove it. I also agree that sometimes developers are put on the defensive when testing takes place.
Here's how I get around it:
Create a logical flow of data from the people who create the requirements to the testers. Support it with documentation. (Use Cases, Object Models, Interaction Diagrams, etc)
Build accountability into the process for everyone involved. This way everyone is clear who has what deliverable.
Continuously check back with the business owners to make sure that you have a clear understanding of what they want, or at least they have repeatedly said that you do. (CYA!)
Track each requirement though the process, from specification through testing and sign off.
If your organization is small enough, let the developers sit in on the meetings where the original requirements are developed.
I can't stress enough how well good communication reduces the number of defects.
The fact of the matter is that defects will happen. They will not be as frequent, however, if you are able to track down the reason easily, as all involved parties will be getting feedback crucial to their development as a team.
I used to work for a company that has offices in India. As a project manager and QA manager, I can assure you that it can be tough. If you're going to hire off shore, don't do contractors, hire a company. That's the only way you'll have accountability. They're like used car salesman, though. You'll want 5 basic developers and they'll try to sell you 5 here, 5 there, and a PM. Stick to your guns. They need the business either way.
Slashdot Mirror
Create defect free software. Too many people (developers, PMs and Clients) that I have worked for as a consultant think that. It doesn't matter how good your testing procedures are if there are no good procedures up to that point. I agree with those who have said that most defects are a result of poor communication, I've got the numbers to prove it. I also agree that sometimes developers are put on the defensive when testing takes place. Here's how I get around it: Create a logical flow of data from the people who create the requirements to the testers. Support it with documentation. (Use Cases, Object Models, Interaction Diagrams, etc) Build accountability into the process for everyone involved. This way everyone is clear who has what deliverable. Continuously check back with the business owners to make sure that you have a clear understanding of what they want, or at least they have repeatedly said that you do. (CYA!) Track each requirement though the process, from specification through testing and sign off. If your organization is small enough, let the developers sit in on the meetings where the original requirements are developed. I can't stress enough how well good communication reduces the number of defects. The fact of the matter is that defects will happen. They will not be as frequent, however, if you are able to track down the reason easily, as all involved parties will be getting feedback crucial to their development as a team.
I used to work for a company that has offices in India. As a project manager and QA manager, I can assure you that it can be tough. If you're going to hire off shore, don't do contractors, hire a company. That's the only way you'll have accountability. They're like used car salesman, though. You'll want 5 basic developers and they'll try to sell you 5 here, 5 there, and a PM. Stick to your guns. They need the business either way.