Increasingly, the quality of delivery in software projects gains considerable weight because increased quality brings down the costs generated by rework and failure handling. Considering that the requirement definition and development phases have a great relevance for the success of each delivery, an effective way to mitigate problems in these stages is with the use of prototypes, since they pass a vision closer to the expected result. But after all, how are prototypes used to bring value in delivery quality?