The validation process will determine whether the product functions are meeting the requirements of the project, whether they meet the organization's objectives, and ultimately, and perhaps most importantly, whether they meet the customer's needs. Usually this process is performed as a final step in the development of a product evaluating the accuracy of the product that always concerns the satisfaction of the needs and requirements of users.
It is interesting that the validation is performed preferentially by a team that does not participate in product development, that is prepared to analyze the product with a customer's perspective and is focused on identifying non-conformities and also suggesting the best resources for the market. It is important that the team is also prepared to verify if the product will integrate into the customer's environment.
It is very important for the quality of a product that all non-conformities inserted during development or maintenance are discovered before the release and because of this it is interesting to apply a validation process. But for how long should this process be carried out? This depends on the fault tolerance that the project may have and there is no defined response but usually the interval of the occurrence of detection of a non-conformity is used as the indicator. This indicator is used to define that the testing investment no longer pays off because of the high time to find a non-conformity.
Do you have tips for more effective testing? Answer the comments below!
Thank you for reading!
Best regards,
Daniel Maurer
Top comments (1)
Great Post Daniel. Based on my experience, better collaboration with developers, product, teams at downstream and upstream have proven to be effective.