The contents of this page has been moved here

Overview This document serves as a guide post for the coverage plan and break up of responsibilites relating to management of the TDP team and associated workflows. Steve jumping into: Prod sync, retro, weekly check-in w/ dev team Sections Daily Stand Up Owner: Miles Current State: Daily stand up to discuss workflows completed the prior day, planned work for the current day, call out any blockers to progress and align on priorities as a greater team.

Background / Next Steps ProofPoint is an e-mail security / screening service that is blocking our e-mail traffic from SendGrid at the IP level see here. In order to resolve, we will need to work with each blocked STT to submit a support ticket / whitelist request for our IP to ProofPoint. This hack.md will outline the STTs we need to work with and planned guidance to provide them in order to resolve. Current Steps: Opened one last support ticket w/ SendGrid If unsuccessful w/ support case, engage STTs below and provide guidance to whitelist our IP. 10.16.23 Update:Identified additional IP associated to our SendGrid account: 159.183.208.143Confirmed, free of ProofPoint block Next Steps: Test deliverability from new IP to ProofPoint STTs, discuss options forward for: maintain two separate IPs, merge to new IP (verify microsoft is playing nice as well) etc.

Sprint 84 10/10/23 - 10/24/23 Sprint Goal Dev:Continue parsing engine developmentComplete SSP Sec (01) and SSP Sec (02) Resolve deployment blocker Coordinate w/ OFA and draft dev contingency plan for future gov shutdown

Background As of June 2023, HHS is deprecating Cisco IronPorts for relaying email to external users and requiring all systems that leverage its SMTP server for communications with external users to obtain an email service provider and share the DKIM and SPF records with the HHS DNS team to enable the system to send emails from .acf.hhs.gov domains. We selected SendGrid as our new e-mail relay STTs blocked by proofpoint Montana Louisiana California Hawaii

Sprint 81 08/30/23 - 09/11/23 Sprint Goal Dev:Continue parsing engine development:1613/1610/1612 TANF Sections: (02 - Validation), (04 - P/V) SSP Sec (01 V, 02 P/V) 2411 - Metadata filters to admin panel ++unblock error report update tickets DevOps:

High level project overview Last update: gantt dateFormat YYYY-MM-DD title TANF Data Portal excludes weekends %% (`excludes` accepts specific dates in YYYY-MM-DD format, days of the week ("sunday") or "weekends", but not the word "weekdays".) section Releases

Sprint 80 08/15/23 - 08/29/23 Sprint Goal Dev:Close out IP parsing work:1613/1610/1612 TANF Sec (01-04) Parsing and Validation Full SendGrid implementation DevOps:

08/01/23 - 08/14/23 New tickets to consider Parsing Cont: 1110 TANF Section 3 ParsingF/O TANF Section 3 Validation F/O Cat 4 Validation 2626 Spike - Parsing Logging (scope from 2486 - Parser Performance) 2411 View metadata on parsed files via admin panel

August 7th, 2023 Tickets Onboarding Sprint 79 prioritiesSDP Onboarding Regional Staff Research RFI research re: new data requirements June 26th, 2023 2559 copy / internal review

Agenda - 07.12.23 Admin: Contract discussionCurrent state: through Jan 2024 Near term: Recompete triggers in a couple of monthsActions:Working with BD team to draft white paper proposal for future state of TDP.Brief to OFA and contracting officer in ~4-5 weeks Draft 1 pager of high priorities for OFA: Move to AWS GovCloud / leave cloud.gov Draft approach for data collection on new reporting requirements from debt bill (largely SA driven analysis)

06/21/23 - 07/04/23 Velocity: Dev (17) Sprint Goal Continue parsing engine development for Section 1 and close out integration test epic (310). UX errors template, follow-on research, onboarding DevOps to resolve utility images for CircleCI and container registry and close out path filtering for CI builds Tickets Completed/Merged

**Challenge: ** The Office of Family Assistance (OFA) aims to promote the economic and social well-being of families, children, individuals, and communities by administering programs and grants at the federal level to states, tribes, and territories (STTs). The largest of these programs is the Temporary Assistance for Needy Families (TANF) program, a $16.5 billion block grant. TANF grant recipients, or STTs, are legislatively mandated to collect individual case record data, which is then aggregated by OFA for descriptive analyses and program performance monitoring. This sensitive data is reported quarterly to the Secretary of Health and Human Services (HHS) and annually to Congress. OFA relies on their legacy TANF Data Reporting System (TDRS) to collect, validate, and store this data. The legacy TDRS system was developed in the late 1990s and has had minor updates since then, consisting solely of a backend system. The system is vulnerable to security breaches, isn’t accessible by all users, and requires substantial manual intervention by end users and system administrators to fulfill their reporting requirements. **Opportunity: ** OFA sought to improve their data collection, storage, and aggregation processes in order to better inform policy decisions affecting vulnerable populations, prevent misuse of grant funds, and greater safeguard highly sensitive personal data.

06/06/23 - 06/20/23 Sprint Goals Continue parsing engine development for Section 1 and close out integration test epic (310). UX to continue STT onboarding (focusing on onboarding CyberFusion users), errors research synthesis, copy for e-mail notification of data submission and errors/transmission reports - 2559 DevOps to resolve utility images for CircleCI and container registry and close out path filtering for CI builds Tickets Carry over In Progress

05/24/23 - Sprint Goals Continue parsing engine development for Section 1 and close out integration test epic (310). UX to continue STT onboarding (focusing on onboarding CyberFusion users), errors research sessions, provide copy for 2509 (e-mail notification for data submission and errors/transmission report) DevOps to resolve utility images for CircleCI and container registry and close out path filtering for CI builds Tickets Carry over In Progress

05/09/23 - 05/23/23 Sprint Goals Release v3.1.0. Continue parsing engine development and close out integration test epic (310). UX will maintain STT onboarding velocity, errors research sessions, provide copy for 2509 (e-mail notification for data submission and errors/transmission report) and iterate on communication method ahead of release v1/beta of downloadable errors report from 1610.1. DevOps to resolve utility images for CircleCI and container registry and close out path filtering for CI builds Tickets Carry over In Progress

5.11 May Cross Sync 1610 Follow Up from Backlog Refinement Once 1610.1 merges, the sub history table will populate a downloadable error report. F/U call to discuss approach to manage user experience ahead of deploying the feature, key notes: Managing user experience, utilizing verbiage to convey messaging of beta feature and set expecations accordingly. Only presnting XYZ errors and will have more robust validation than legacy system, need to have clear messaging they need to continue correcting errors off the legacy reports and the downloadable TDP report will be incomplete until parsing finishes. OFA aligned in low tech lift approach and managing comms via some form of wording in the column header/file name/file content itself - would love UX input here Potential for some type of e-mail communication needed to introduce the beta feature / continue to keep up to date with roll outs as the report matures ID a subset of users to target for further research

04/25/23 - 05/09/23 Velocity: 25 Sprint Goal Tickets Completed/Merged #2489 - API endpoint security issue #1122 As a data analyst, I am able to see validation errors for a file in order to remedy them (error column) #1336 - Request access notification and Django Filter #2274 As tech lead, I want our user approval flow tested

04/11/23-04/25/23 Velocity: 26 Sprint Goal Close out TANF and SSP section 1 parsing tickets, continue further parsing engine development. Start final planned work for v3.1.0 - access request email notification and updating Django Admin Console. UX will finalize synthesis findings/format, provide copy of KC videos, continue STT onboarding and .csv errors research. DevOps to finalize utility image(s) for CircleCI pipeline, container registry creation, and documentation before beginning to leverage path filtering for CI builds. Tickets Completed/Merged #1543 Add Gunicorn settings to correctly receive header #1544 - [SPIKE] Add Nginx configuration - increase security and performance

Recurring Meetings Daily Stand UpDiana to drive day to day Resources to support: Spr 72 planning doc, daily stand up notes - no major call outs, Andrew to continue driving Parsing Engine development. KC Videos 1 and 2 to be submitted to ACF YT team 5.1. George has personal situation going on, Andrew to manage directly with him 1:1. If Dev needs to pull in more tickets, Andrew can drive, priority will be 3.2 Parsing as long as 1336 and 2489 are complete for 3.1 release. Note: Dev to work on cross communiciation, asking for commitment on reviews and timelines from peers during SU Backlog Refinement Andrew to lead discussion of new tickets UX to attend per usual operating process