Introducing
new software QA processes in any an organization will largely depend on the
size of that organization and the risks associated with it.
1. Large/Medium Organizations: For projects which have high risk associated with them, both in terms of revenue, lives or property, serious management Buy-in is required and a formalized QA process is necessary. If required, external stakeholders or new Vendors can be introduced to the organization that has prior expertise and domain knowledge depending on the needs of the Project involved.
2. Small Groups or Projects: Ad-hoc processes may be appropriate, depending on the type of customers and projects. A lot will depend on team leads or managers, feedback to developers, and ensuring adequate communications among customers, managers, developers, and testers.
Most of the focus will be on the following area in both the above scenarios:
(a) Analyzing Requirements in a clear, complete and testable way so that the requirements specified in Project documentation is formalized for further QA process ,
(b) Periodic review and Design inspections by core functional group.
(c) Post-mortems/retrospectives among all members of development and testers to make process enhancements.
1. Large/Medium Organizations: For projects which have high risk associated with them, both in terms of revenue, lives or property, serious management Buy-in is required and a formalized QA process is necessary. If required, external stakeholders or new Vendors can be introduced to the organization that has prior expertise and domain knowledge depending on the needs of the Project involved.
2. Small Groups or Projects: Ad-hoc processes may be appropriate, depending on the type of customers and projects. A lot will depend on team leads or managers, feedback to developers, and ensuring adequate communications among customers, managers, developers, and testers.
Most of the focus will be on the following area in both the above scenarios:
(a) Analyzing Requirements in a clear, complete and testable way so that the requirements specified in Project documentation is formalized for further QA process ,
(b) Periodic review and Design inspections by core functional group.
(c) Post-mortems/retrospectives among all members of development and testers to make process enhancements.
For more on this, log on to:- http://www.qainfotech.com/qa_process_management_services.html
No comments:
Post a Comment