Attachment C Sprint Level Quality Bars (QASP like) For Comment.pdf
PDF 109 KB Posted
- Attached to
- Agile Refactoring & Sustainment of Legacy Applications to Salesforce Public Sector Solutions (PSS)
- Solicitation number
- FA7014Agile-Refactoring-Sustainment
About this file
This document is an Attachment C detailing Sprint-Level Quality Bars, which appears to be a quality assurance and software development guidelines document. The document outlines specific quality metrics for software development across five key areas: testing, code style/linting, accessibility, security, and deployability. The requirements include maintaining approximately 90% meaningful automated test coverage, zero errors/warnings at code merge, zero critical automated 508 accessibility errors, no high/critical security findings, and the ability to perform one-command builds with documented rollback procedures. Additionally, the guidelines mandate updating documentation, including software version description (SVD) and release notes each sprint, with clear traceability to project stories and acceptance criteria.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Attachment C — Sprint‑Level Quality Bars (QASP‑like) — For Comment Tests: ~90% meaningful automated coverage (unit + integration); all tests run in pipeline.
Style/Lint: 0 errors/warnings at merge.
Accessibility: 0 critical automated 508 errors; manual checks on changed UI.
Security: No high/critical SAST/DAST findings; SBOM delivered and updated.
Deployability: One‑command build; documented rollback; successful deployment to staging/prod as applicable.
Documentation: SVD/release notes updated each sprint; traceability to stories and acceptance criteria.
Attachment C — Sprint‑Level Quality Bars (QASP‑like) — For Comment
File details come from the government source that posted it. Updated .