QA plays a Pivot role right from the start of the generation
of Requirements, so as to understand the real business needs of the Customer. Participation
of QA in the course of feature preparation, arrangement and development will
make huge impact to business, for the reason that if QA understand the product
and the domain it can lead to early identifications of gaps and fruitful ideas that
can enlarge and enhance quality in depth of the deliverable's.
QA works very close to the business analysts to understand
the user’s needs. Engagements of QA with
the developers, when they discuss architecture will impact the product quality,
because at this time of SDLC, QA sets up the user expectations, technical
limitation can be worked out based on the functional solutions planned and if
there needs to be any change in the technical architecture it can be worked
very early in the SDLC. The knowledge gathered by QA will not only help to
focus the testing efforts on the most critical areas of the program, but will
also help QA determine the areas of risk to the business. Some of other benefits
are:
- Understand the Functionality well in advance.
- Propose new enhancement or feasibility early in the product life cycle.
- Creating testcases based on the actual Business need.
- Organized usability testing.
- Performing exploratory testing on early builds.
No comments:
Post a Comment