
Ideally there would be documentation, checklist or some form of standard procedure for a project team to follow so they can be 100% sure that what they are doing in regards to a system build, infrastructure build etc is correct and will result in the desired output.
In my experience I have seen that a project team can only be sure that what they have requested to be made was made correctly when they or the client test it.
Imagine that you buy a car and the only way to know that the brakes work is to drive it at 100 kph / mph and then press the brake pedal and hope.
If there is no checklist to ensure that the project team makes the right request or that the build team know that they have built something correctly then this creates a risk. As no one knows with 100% certainty that they will not face issues associated with this work during later stages of the project. Therefore this is a risk to the delivery of the project and the organisation´s reputation
Consequently, it would be very beneficial to an organisation if there was a standard checklist that outlined exactly what has to be requested and then built (e.g. a car cannot be requested or built without a braking system). This checklist would give everyone involved a high level of confidence that the later stages of the project will proceed well and to plan