FE: DUW: Validate content doc and flow diagram by examining wizard code

[wesrowe]

Description

User story

AS A PO/PM/Stakeholder I WANT to be sure that the documentation that we have for the Discharge Upgrade Wizard accurately represents the product in production SO THAT we base our review of the documentation on the current best understanding.

Engineering notes / background

Docs to validate:

• Mural of logic – Note: for clarity's sake you might want to start a new Mural without some of the double screenshots (Wes create those whilst QAing radio component upgrade)
• Content doc in Github

Analytics considerations

Quality / testing notes

Acceptance criteria

Consider

• Design / Accessibility reviews
• Collab cycle requirements
• Device sizes (mobile first)
• Documentation updates / Change management < - Content model documentation
• Testing notes

• [x] PM/DM have migrated Github content doc to a Sharepoint Word doc
• [x] Checked flow chart in Mural, updated as needed to represent all the possible branches of the wizard
• [x] Checked Word content doc, updated as needed to include all content that is presented on all logic branches
• [ ] Added any missing elements into both documents, with some indicator that they are new findings
• [ ] Ensured CAIA (content team) was notified in their intake ticket that this review has been completed

[wesrowe]

@chriskim2311, this is a first step toward rebuilding the DIscharge Upgrade Wizard. We may want to pull this into sprint, so take a look before planning if you can. Be ready with points, questions. Thanks!

[chriskim2311]

Just taking a quick glance, there are some UI issues with helper text that was noted in the mural that I have verified. Going through all paths and verifying branching, helper text, and results match up with documentation I agree with Randi's 5 estimate.

[jilladams]

From planning: let's migrate the Github content doc to a Sharepoint Word doc, for ease of use. PM/DM will get that done before this ticket begins.

[chriskim2311]

@jilladams For this ticket, I have migrated the content doc from github to sharepoint and updated the flow to what we have currently.

Sharepoint Word Doc: Discharge Upgrade Wizard Content Doc

I also validated the code/content with Jordan's mural flow and that looks good on my end no issues to note.

[jilladams]

@thejordanwood - @chriskim2311 has a source of truth doc for DUW content in prod, and has cross-checked his SharePoint doc against your Mural.

Sharepoint - https://dvagov.sharepoint.com/:w:/r/sites/SitewidePublicWebsites/_layouts/15/Doc.aspx?sourcedoc=%7BE399B79E-68AE-41E2-82AE-042F5A7DA6F4%7D&file=DischargeUpgradeWizardContent.docx&action=default&mobileredirect=true

I think we could close both this ticket and #15532 now, and share with CAIA, but if it seems wise to have Jordan put eyes on the content doc, or get me to step through it, etc: I'm happy to. Let me know your confidence levels.

[jilladams]

(I'm gonna go ahead and share with CAIA.)

[thejordanwood]

@jilladams I've looked at the content doc and pulled content from there to show all of the results screen versions in the Mural board. I'll go ahead and close my ticket.

[jilladams]

Closing, in that case!