Definition of Done User Story Checklist rev.1.1.docx
DOCX document 82 KB Posted
- Attached to
- Federated Search
- Solicitation number
- Not on record
About this file
This is a Definition of Done checklist document for the Bomb Arson Tracking System (BATS) Modernization project at the Department of Justice Bureau of Alcohol, Tobacco, Firearms and Explosives (ATF), developed in partnership with the Office of Science & Technology and Office of Intelligence Operations.
The document establishes detailed quality assurance and acceptance criteria organized into two sections: a User Story checklist containing 18 tasks and a Sprint checklist containing 9 tasks. The User Story checklist requires completion of all assigned tasks, code review, acceptance criteria verification, non-functional requirements validation (including page load times of 1-2 seconds, carousel thumbnail optimization, and email delivery within 5-15 minutes), Section 508 compliance testing, test coverage completion (unit, end-to-end, and functional testing), security vulnerability scanning, and Product Owner acceptance. The Sprint checklist ensures that all user stories meet Definition of Done standards, all unit tests pass, bugs are resolved, incomplete stories return to the Product Backlog, environments are properly prepared for release, and testing is conducted in the QA/Test environment with production pushes from Staging. Additionally, the document includes a comprehensive Section 508 Revised Standards Applicability Checklist for the Confidential Informant Master Registry and Reporting System (CIMRRS), detailing WCAG Level A and Level AA electronic content requirements, software and hardware standards, support services documentation standards, and functional performance criteria for accessibility compliance across various user capabilities.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFI Q and A.docx | DOCX document | |
| 9 - ATF - Attachment 2 - ATF Enterprise Standard Technologies - June2023.docx | DOCX document | |
| ATF Data Governance Policy.pdf | ||
| Style Guide_ Final Version.pdf | ||
| Federated Search PWS.docx | DOCX document | |
| ATF Federated Search Request For Information (RFI).docx | DOCX document | |
| ATF DG Handbook - Version 4.2.docx | DOCX document | |
| ATF Agile Playbook.pdf#search=agile playbook.pdf |
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: Definition of Done User Story and Sprint Department of Justice Bureau of Alcohol, Tobacco, Firearms and Explosives (ATF) Office of Science & Technology (OST) in partnership with Office of Intelligence Operations (OIO) United States Bomb Data Center (USBDC)
Definition of Done User Story Checklist Bomb Arson Tracking System (BATS) Modernization
Definition of Done User Story Checklist
| No. |
| Task |
| Status |
| 1 |
| Each task in User story is complete. |
| 2 |
| All commits are code reviewed. |
| 3 |
| Acceptance criteria have been completed and verified. Acceptance criteria will be provided by the Product Owner and must be met. |
| 4 |
| Non-functional requirements such as performance, maintainability, scalability, availability, and operability have been implemented or validated and tested. (Performance criteria shall include: Page load should be 1-2 seconds at the most, thumbnails of photos in a carousel, database indexing as needed, and emails sent within a reasonable amount of time 5-15 minutes.) |
| 5 |
| Key technical functionalities (such as building in page usage data collection, Section 508 compliance, security audit capabilities (who created a record, when a record is modified) have been verified |
| 6 |
| Test coverage is complete. |
| 7 |
| Unit test coverage is complete. |
| 8 |
| Any new end-to-end tests are created and existing end-to-end tests with a passing end state when there are no known defects associated with it. |
| 9 |
| Functional test cases occurring after each code commit to verify code does not have any issues with existing code. |
| 10 |
| All issues found during testing that were deemed non-critical (does not affect functionality or performance) are documented as defects and flagged as technical debt. |
| 11 |
| Modifications to the Regression Test Suite have been identified and implemented. |
| 12 |
| All deployment steps are scripted or manual steps documented |
| 13 |
| Documentation has been updated (to include any SOPs or other supporting documentation). |
| 14 |
| Comply to the 508-compliance checklist attached to the document |
| 15 |
| User story has been Section 508 tested with no known critical issues (others are documented as technical debt defects). |
| 16 |
| User story has been communicated and/or demonstrated, as appropriate to the Product Owner during the development process, to address any issues prior to acceptance |
| 17 |
| The code has been found to contain no security vulnerabilities threats. The security scans are conducted monthly |
| 18 |
| The Product Owner and/or GTM has accepted the User story. |
Definition of Done Sprint Checklist
| No. |
| Task |
| Status |
| 1 |
| Definition of Done of each user story in the sprint is met |
| 2 |
| All unit tests are passed |
| 3 |
| All bugs are fixed |
| 4 |
| User stories that are not completed during a Sprint must be moved to the Product Backlog and earn their way into the next Sprint. |
| 5 |
| Comply to the 508-compliance checklist attached to the document |
| 6 |
| Product Backlog is updated |
| 7 |
| Will confirm all environments are prepared for release – i.e. confirming no unintegrated work in Dev/Staging environment, Continuous Integration is working, and automated regression test and test data are validated. |
| 8 |
| No testing will be performed in the Staging environment. It will be done in the QA/Test environment. |
| 9 |
| Production push will be from the Staging environment. |
Reference Documents:
image1.jpeg image2.emf
CIMRRS 5.1 508 Checklist.docx Revised 508 Standards Applicability Checklist
This checklist will help you communicate accessibility requirements for information and communication technology (ICT) items in contracting documents or systems requirements documentation based on the Revised 508 Standards.
Name of ICT Item: Confidential Informant Master Registry and Reporting System (CIMRRS)_____
Electronic Content Standards
WCAG Level A Requirements
☒ 1.1.1 Non-text Content
☐ 1.2.1 Audio-only and Video-only (Prerecorded)
☐ 1.2.2 Captions (Prerecorded)
☒ 1.3.1 Info and Relationships
☒ 1.3.2 Meaningful Sequence
☒ 1.3.3 Sensory Characteristics
☒ 1.4.1 Use of Color
☐ 1.4.2 Audio Control
☒ 2.1.1 Keyboard
☒ 2.1.2 No Keyboard Trap
☒ 2.2.1 Timing Adjustable
☐ 2.2.2 Pause, Stop, Hide
☐ 2.3.1 Three Flashes or Below Threshold
☒ 2.4.1 Bypass Blocks (not required for non-web documents and software)
☒ 2.4.2 Page Titled
☒ 2.4.3 Focus Order
☒ 2.4.4 Link Purpose (In Context)
☒ 3.1.1 Language of Page
☒ 3.2.1 On Focus
☒ 3.2.2 On Input
☒ 3.3.1 Error Identification
☒ 3.3.2 Labels or Instructions
☒ 4.1.1 Parsing
☒ 4.1.2 Name, Role, Value
WCAG Level AA Requirements
☐ 1.2.4 Captions (Live)
☐ 1.2.5 Audio Description (Prerecorded)
☒ 1.4.3 Contrast (Minimum)
☒ 1.4.4 Resize Text
☒ 1.4.5 Images of Text
☒ 2.4.5 Multiple Ways (not required for non-web documents and software)
☒ 2.4.6 Headings and Labels
☒ 2.4.7 Focus Visible
☒ 3.1.2 Language of Parts
☒ 3.2.3 Consistent Navigation (not required for non-web documents and software)
☒ 3.2.4 Consistent Identification (not required for non-web documents and software)
☒ 3.3.3 Error Suggestion
☒ 3.3.4 Error Prevention (Legal, Financial, Data)
WCAG Conformance Requirements
☐ Conformance Level (level AA)
☐ Full Pages
☐ Complete Processes (for software, see E207.3)
☐ Only Accessibility-Supported Ways of Using Technologies
☒ Non-Interference
Software Standards
☒ 502 Interoperability with Assistive Technology
☒ 503 Application
☐ 504 Authoring Tools
☐ Include applicable standards (WCAG, Support Services & Documentation Standards, Functional Performance Criteria)
Hardware Standards
☐ 402 Closed Functionality
☐ 403 Biometrics
☐ 404 Preservation of Information Provided for Accessibility
☐ 405 Privacy
☐ 406 Standard Connections
☐ 407 Operable Parts
☐ 408 Display Screens
☐ 409 Status Indicators
☐ 410 Color Coding
☐ 411 Audible Signals
☐ 412 ICT with Two Way Voice Communications
☐ 413 Closed Caption Processing Technologies
☐ 414 Audio Description Processing Technologies
☐ 415 User Controls for Captions and Audio Descriptions
☐ Include applicable standards (WCAG, Support Services & Documentation Standards, Functional Performance Criteria)
Support Services & Documentation Standards
☒ 602 Support Documentation
☒ 603 Support Services
Functional Performance Requirements
The following apply when the 508 Standards do not address one or more functions of the ICT, or when determining “equivalent facilitation.”
☒ 302.1 Without Vision
☒ 302.2 With Limited Vision
☒ 302.3 Without Perception of Color
☒ 302.4 Without Hearing
☒ 302.5 With Limited Hearing
☒ 302.6 Without Speech
☒ 302.7 With Limited Manipulation
☒ 302.8 With Limited Reach and Strength
☒ 302.9 With Limited Language, Cognitive, and Learning Abilities
This checklist was developed by the U.S. Federal Government Revised 508 Standards Transition Workgroup. Members include the U.S. Federal CIO Council Accessibility Community of Practice, the U.S. Access Board, and the General Services Administration.
Checklist Reviewed/Updated: March 2022
File details come from the government source that posted it. Updated .