Quality Assurance Best (and Good) Practices

by E.R. Williams

1. Prepare and develop a quality management and assurance plan (incorporated) for QA- (which includes verification & validation, test methods/testing, and quality control) in compliance with standards and tailored to the project or program
2. Conduct an assessment, as required
3. Select and use QA automated test tools - Rational, Mercury, Silk, etc.
4. Review and audit plans, processes, and activities. Develop a plan to perform the required activities, share with the affected functional areas or groups. Tailor to the project or program.
5. Track errors, defects, and identify trends
6. Review business plan, strategy, financial/budget, and the contract requirements, standards, and regulations
7. Develop and use procedures and checklists to perform and conduct QA
8. Document all QA activities/processes for each phase, as required
9. Create test strategy based on solution/approach/methodology
10. Create test strategies and plans based on requirements and design
11. Participate, perform or witness and certify functional and system tests
12. Participate on change and configuration control review and corrective action review team/board
* Identify and select the appropriate tools, applications, and methodologies

Worst/Bad Practices
1. Just using QA for only testing and not Verification and Validation/Testing because QA ensures compliance and building in quality (Must allow for the review of the solution and any contract requirements, project and product requirements, the development methodology and processes in the beginning of the project or program to set up the QA verification and validation process. If Quality Assurance is not involved early, this can not take place.)
2. Not introducing QA early in a project and program


Previous post:

Next post: