Yes, I strongly believed that verification can takes place at any time in a project and most importantly during the execution phase. I think even after the project completion, verification should still be conducted, if even if the changes might not be edited, it will provide an idea of how to amend future similar projects.
I believe it is a rigid rule that verification takes place during the execution phase of a project. Since verification is done to ensure design outputs meet design inputs, beginning verification earlier during the planning phase would not be ideal since the design inputs and outputs may not be finalized yet. If there are any problems or delays in finalizing design inputs and outputs, beginning verification too early may result in needing to repeat parts of verification if any design changes occur.
Additionally, there could be additional problems if the verification process extends into the closing of a project. If it has not yet been completely verified that the design outputs meet the design inputs, it would not be efficient to begin closing the project.
I believe that verification should take place during the Execution phase of the project, but it does not necessarily need to be a rigid rule. As seen in the first simulation, there were gaps in the verification protocol and changes that had to be made, which later resulted in an effective execution. Verification should take place during execution due to the fact that during verification, you are trying to ensure that the design outputs meet the design inputs, which can really only be done after execution. However, when developing a product, if something were to go wrong during the execution phase, where the outputs do not necessarily meet the inputs, the verification protocol may be adjusted to ensure the outputs meet the customer’s needs. At time of product development, verification is very active, and many tests are being done to ensure the design outputs are meeting design inputs, which is why verification can flow into other processes.
