A short document that captures the criteria with which the software's quality will be judged at various stages of the project.
What this isA short document that captures the criteria with which the software's quality will be judged at various stages of the project.
Why it's useful
Way too many products get released before they're truly ready. But if it's released before it's really ready, everyone will pay. The customer will have to live with a buggy product, the development team will have to hang on making corrections... Products and applications sometimes get passed from Development to Test group before their time. When this happens, the test group can't execute their schedules because the product may not work well enough for them to execute their test suites without encountering an overwhelming number of defects. Having a software release criteria document makes sure the team defines up front how well the software must work before it is released to the next stage of the process.
How to use it
Draft this document during Execution phase, as detailed design and coding is occurring, so that the criteria are ready in time for the handoffs from developers to integration, integration to system testing, etc.
©Copyright 2000-2017 Emprend, Inc. All Rights Reserved.
About us Site Map View current sponsorship opportunities (PDF)
Contact us for more information or e-mail firstname.lastname@example.org