|
• A great deal of dependency is on the size of the organization and the
risks involved with pursuing a software project. For
firms with high risk projects (e.g. involving human
lives or property damage etc.), there is a critical
requirement of high quality testers to be hired and a
complete well defined software QA process is necessary. • In low risk situations, the management and organizational interest in QA implementation would be a slower process. QA process should be balanced with the efficiency so that proper administration is maintained. • For small ad lesser complex projects, an ad-hoc process is preferable, which depends on who are the customers and what the projects are about. The team leads or managers will have high responsibility and much dependency is on feedbacks that are provided to the developers, maintaining good communication among customers, developers, managers as well as testers. • The most important effort requiring tasks will be a) requirements management processes, which needs an objective of clear, complete and testable software requirement specification along with requirements and/or design documentation (b) design inspections and code inspections, and (c) post-mortems/retrospectives. • Other possibilities include successive incremental cross functional and/or self managed teams or groups approaches like 'Kaizen' methods of continuous process improvement, the Deming-Shewhart Plan-Do-Check-Act cycle, and others. |
| Sponsored Links: |
| << back |