Product Discovery: Remaining work for Paper Form Sync

[pacerwow]

Issue Description

As PM I want to understand what work has been completed for Paper Form Sync and what known work is remaining for this initiative so that I can prioritize and plan the remaining work. As a result of this story being completed, we should be able to begin working on these product backlog items.

Tasks

• [ ] Review the 526 Paper audit spreadsheet
• [ ] Compare the 2022 526 paper form with the digital form to see if there are any differences not noted in the spreadsheet
• [ ] Meet with OCTO & VBA to understand and document if there are any gaps after completing the above
• [ ] Write new PBIs or edit existing ones that describe the work (see AC below)
• [ ] Prioritize these PBIs according to the severity noted in the spreadsheet
• [ ] Meet with Research, Design, and Engineering disciplines (as required) to help identify key assumptions and knowledge gaps
• [ ] the required roles and skills for each PBI are labeled on each PBI (where possible)

Acceptance Criteria

• [ ] The 526 Paper Audit spreadsheet has been reviewed
• [ ] Ensure that OCTO and VBA have been given a chance to identify any work that isn't on the 526 Paper Audit spreadsheet
• [ ] Product backlog items (PBIs) are created for each known piece of work
• [ ] PBIs are made visible to the team
• [ ] For each PBI, a clear, concise problem statement is written
• [ ] For each PBI, key assumptions and knowledge gaps are identified
• [ ] PBIs are prioritized
• [ ] Required roles and skills for each PBI are tagged as labels on the user story
• [ ] Results are shared in a Sprint Review

Additional information

We hit pause on the paper form sync work outside of Toxic Exposure. Where exactly did we leave this? What's done and what's remaining? What should we start on first? What might require design, front end engineering, backend engineering?

Some tickets already exist for the paper form sync work. I suggest doing the research/discovery first to determine what we did and what we need to do, then look at existing tickets to see if any of those can or should be updated. Existing tickets may also give you a clue into what was delivered, but beware that there may be inconsistencies. Your best source of truth is the form in staging. A lot of work has gone into discovery of this already so most, if not all, of the differences between paper and digital are known. This story is simply to refresh and reevaluate where we are so we can plan the upcoming work.

The last known source of truth is this spreadsheet in SharePoint.

[mayacarrolluxa6]

@pacerwow I have concerns about including this ticket in our Sprint 10 goals. Ideally, the HCD group would participate, but from my understanding, the the paper for sync is a lower priority than the remaining submission experience work from Shannon’s perspective. Additionally, with our reduced capacity this sprint, I’m not confident we have the bandwidth to take this on. I recommend removing it from our Sprint 10 goals and product backlog.