How work is accepted

How work is accepted

We work toward the standards set forth in 18F's standard Quality Assurance Surveillance Plan (QASP) The government uses the QASP to monitor the quality of a vendor’s deliverables and performance. This helps the government measure vendor performance and ensure it reaches required levels as specified in the contract. The QASP provides the government with a proactive way to identify and avoid deficient performance.

How design work is reviewed and accepted

The Product owner reviews and accepts design work throughout the project. (Design work is both user research and designing interfaces. They rely on each other.) Generally, the PO reviews design work during co-working sessions or async and checks a "PO approved" box in the task list when the designs meet their approval.

Design-related QASP provisions

User research: Usability testing and other user research methods must be conducted at regular intervals throughout the development process and not just at the beginning or end of the process.
Accessible user interface: Web Content Accessibility Guidelines (WCAG) 2.1 AA standards.

How technical work is reviewed and accepted

The technical lead reviews and accepts technical work throughout the project. (Technical work includes things like code styling, testing, and documentation.) Tech lead reviews often take the form of code reviews on Github pull requests.

See the Code Review section of the Release Engineering Process page.
See the QASP section of the Release Engineering Process page for technical QASP provisions.