3. Decentralized test teams
Some projects that I have consulted for, have a decentralized
testing approach where each individual business process team,
technical team (ABAP/4), and Basis (security) team conduct their own
testing in the absence of a QA/testing team.
The decentralized method suffers from various drawbacks including
redundancy, inconsistency, lack of standards, missing testing
metrics, unreported test results, limited managerial visibility,
limited test coverage, chaotic defect resolution, no independent
verification of test results, etc.
Projects with a decentralized test approach perceive control as a
significant advantage of decentralized testing. With decentralized
testing each team has the independence and control as to how their
particular area will be tested based on their own defined test
procedures.
The perceived benefits from decentralized testing do not offset its
drawbacks. A more robust approach for testing an ERP system is
centralized testing where there is a QA team for defining the
standards and procedures for the various testing cycles and
documenting the test plan, lessons learned, UAT plan and the test
strategy. The test procedures and test strategy include what test
case templates will be used, how and what metrics will be reported,
how peer reviews will be conducted, ensuring that all test
requirements have been met, etc. In addition to the QA team under
the centralized model the testing team provides expertise for
executing test cases whether manually or with automated test tools.
The testing team also provides independent verification for the test
results since the testers were not associated with the configuration
of the transactions, workflow development, creation of user roles,
or the development of the RICE (Reports, Interfaces, Conversions,
and Enhancements) objects, etc.
Please note:
All contents hereby presented are copyrighted material from Jose
Fajardo.  Copyrighted 2002. All rights reserved. Must obtain
permission from Jose Fajardo to reproduce, disseminate or publish
this article. Email:
jfajardo@octanesystems.net
