IVVQ (Integration, Verification, Validation, and Qualification) generally takes place
incrementally in an Agile project rather than being done at the very end of the project:
Integration - happens continuously throughout the project. As new code is
developed, an integration test is typically run to ensure that it is compatible
with other code. This is a far better approach than waiting until the very end
of the project to see if everything works together.
Verification - typically means compliance with written specifications and
written requirements. That is limited in Agile which is also a big advantage.
Instead of relying heavily on written requirements documents that are very
subject to communications errors, Agile relies much more heavily on direct
communication with the customer. That should minimize
miscommunication and errors in requirements.
Validation - typically means how well the solution fills the intended need
regardless of what the requirements say. That is another area where Agile is
very strong. In a traditional plan-driven project, validation might not happen
until the very end of the project in the form of a user acceptance test and by
that time it may be too late to make significant corrections. In an Agile
project, it happens continuously - at least at the end of every sprint if not
sooner, the customer sees the feature that is being developed and has an
opportunity to accept it or reject it and provide feedback.
Qualification - typically means “beta testing” to actually put the product
into operational use (or simulated operational use) and see if it really
performs effectively in an operational environment. That is also done much
more incrementally in an Agile project where the solution would typically
be broken up into incremental releases that can be tested in an operational
environment before the entire project is complete.
In simple terms, there is no formal IVVQ process in an Agile environment because instead of
being a separate phase, it is completely integrated into the Agile development process and
happens incrementally throughout the project which I think can be a much more effective
approach.
Testing constitutes a core activity in system development projects, especially within domains
such as defense, aerospace, space, healthcare, and other safety-critical industries. To ensure
that complex systems meet both technical specifications, user requirements, and regulatory
standards, organizations often rely on the structured framework known as IVVQ –
Integration, Verification, Validation and Qualification. This framework provides a
systematic and traceable approach from early design to final certification.
The purpose of this text is to provide a holistic, academically oriented discussion of testing
within the IVVQ framework. Testing is examined here as a technical activity, a
methodological discipline, and an organizational practice.
0
