You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 7, 2021. It is now read-only.
"Quick submit," also know as "the 8%" by NJ, is the minimum required questions to start a SNAP application.
Note: This is a "soft MVP," in that we do not intend to launch to production because drastically increasing the number of "quick submit" applications could have serious negative impacts on workload for caseworkers (they'll ultimately need to collect all the information from applicants) and applicants ("quick submit" is a faster way to start an application, but increases the time to receiving benefits). We'll study this and eligibility checking in user research to determine MVP2.
Why did we choose this MVP?
Policy: A quick submit experience is required by regulation (name, address, signature)
Timing: Give design a chance to catch up to engineering
Testing: Engineering can start QA and UAT, ensuring the data gets from our form through the system successfully (this takes up to an entire month for the mainframe system, FAMIS)
Agile: Be more agile, help us find extra details/issues we might be missing in an end-to-end experience
Required steps
Design:
Get answers to open questions from NJ stakeholders Get answers to open questions from NJ stakeholders #250 (includes defining minimum "quick submit" questions required to initiate an application and supporting folks experiencing homeless)
Design the post-quick submit flow (potentially includes submitting signatures by directing people to the doc upload tool) Design the post-quick submit flow #251
Design checking the status of an application
Conduct a content review of quick submit messaging, including questions, error messaging, confirmation pages, etc. (Ticket forthcoming)
Eng:
Build pre-submit review page (already designed)
Build checking the status of an application (not yet designed)
"Quick submit," also know as "the 8%" by NJ, is the minimum required questions to start a SNAP application.
Note: This is a "soft MVP," in that we do not intend to launch to production because drastically increasing the number of "quick submit" applications could have serious negative impacts on workload for caseworkers (they'll ultimately need to collect all the information from applicants) and applicants ("quick submit" is a faster way to start an application, but increases the time to receiving benefits). We'll study this and eligibility checking in user research to determine MVP2.
Why did we choose this MVP?
Required steps
Design:
Eng:
Build pre-submit review page (already designed)
Build checking the status of an application (not yet designed)
[Epic] FE/BE: Form submission integration testing FE/BE: Form submission integration testing #222
[Epic] Frontend: Section 0 — Account and application screens [Epic] Frontend: Section 0 — Account and application screens #23
[BE] Set up ability to send emails from GraphQL server#271
[BE] Create endpoint for resetting a password after a user confirms their hint question [BE] Create endpoint for resetting a password after a user confirms their hint question #189
[FE] Implement Spanish translation: Section 0 — Account and application screens [FE] Implement Spanish translation: Section 0 — Account and application screens #62
[FE] Implement Spanish translation: Quick submit [FE] Implement Spanish translation: Quick submit #63
FE: Quick Submit FE: Quick Submit #221 (Add the logic and integration with backend to support the quick submit functionality.)
[FE] Add session support [FE] Add session support #177
[FE] Standard error messages on the front-end [FE] Standard error messages on the front-end #194
QA
The text was updated successfully, but these errors were encountered: