Agile frequent verification and validation
Agile frequent verification and validation
Any iteration in agile development must produce artefacts, typically code, that pass the phase of verification and
validation.
Therefore, all iterations must have phases like this.
For requirements and design, the verification and validation is the result of peer reviews with team members and
with the customer
For coding, verification and validation is done by code reviews, unit testing and functional testing.
Basics of verification
Am I building the right product
Determining if the system complies with the requirements and performs functions for which it is intended and
meets the organization’s goals and user needs. It is traditional and is performed at the end of the project.
Am I accessing the right data
High level activity
Performed after a work product is produced against established criteria ensuring that the product integrates
correctly into the environment
Determination of correctness of the final software product by a development project with respect to the user needs
and requirements
Basics of validation
Am I building the product right
The review of interim work steps and interim deliverables during a project to ensure they are acceptable. To
determine if the system is consistent, adheres to standards, uses reliable techniques and prudent practices, and
performs the selected functions in the correct manner.
Am I accessing the data right (in the right place; in the right way).
Low level activity
Performed during development on key artefacts, like walkthroughs, reviews and inspections, mentor feedback
Demonstration of consistency, completeness, and correctness of the software at each stage and between each stage
of the development life cycle.
Importance of Verification and Validation in Agile
An Agile Methodology does NOT mean that there will be « frequent changes in requirements. »
What Agile specifically does is to begin with very high level view of the requirements at commencement, and
through the iterative process to begin honing those requirements with your stakeholders as they begin to interact
with the product itself.
Leave a Reply
You must be logged in to post a comment.