Staging Review - Claims & Appeals - 526 Wizard updates

vhenry07 commented 3 years ago

Steps to complete Staging Review:

[x] VFS Product Manager: Create this issue and fill in your team and feature name in the title.
[x] VFS: Link to this issue once created in #vfs-platform-support in Slack; tag @vsp-product-support-members.
[ ] VSP: Schedule meeting with VSP reviewers and requesting team attendees (as listed below)
[x] VFS: At least 4 days before scheduled meeting, you must complete list of artifacts below
[x] VFS: Verify that access information has been provided for the tool or feature in staging. Do not put staging credentials in your va.gov-team ticket; store or reference them in a .md file in the va.gov-team-sensitive repository.
[ ] VSP: Create feedback tickets and link to the Staging Review ticket (if no feedback, please comment stating that).
[x] VFS: Respond to VSP feedback tickets.
[ ] VFS: Update this ticket with the product’s launch date after it has gone live.
[x] VSP: Update Platform Collaboration Point Tracker.
[ ] VFS: Close this ticket when the review is complete.

Artifacts

Link to product outline
Link to the tool or feature in staging. Wizard in staging. Do not put staging credentials in your va.gov-team ticket; store or reference them in a .md file in the va.gov-team-sensitive repository.
Staging test-user information (if applicable)
Link to content brief (if applicable)
Link to or specify the artifact that represents this initiative's content source of truth (for example, mockup, prototype, Github, Word outline, or elsewhere)
Link to release plan with the "Planning" sections completed (in each section: Phase I, Phase II, Go Live)
Link to your product test cases/test plan in TestRail with test execution logs (learn more) for QA practice area review
Link to your Coverage for References and Summary(Defects)* reports in TestRail for QA practice area review
Link to verification that accessibility checks are complete:
- (preferred) Link to your TestRail VSP accessibility test plan template. OR
- Link to a doc in your product folder that indicates all required checks from the accessibility staging review prep doc are complete.
List of known issues (with links to tickets when applicable)

Meeting attendees from requesting team

Product Manager (required): Veronica Henry
DEPO product lead (recommended): Matt Self
Anyone else from your team who significantly contributed to the artifacts provided (required): Robin Garrison
Content, IA, accessibility, and QA specialists (if applicable): name(s)

Scheduling

What is your preferred time slot per the VSP Collaboration Meetings Calendar? 7/1, 1:30

Please note:

All times are shown in ET.
Available time slots are indicated with [CALENDAR BLOCK].
When you reserve a time slot, the reserved meeting will show up alongside the [CALENDAR BLOCK].
Please select a time slot at least 4 business days from request date.

Additional information

Please refer to the VSP Collaboration Cycle README on Github for more information about the Collaboration Cycle.

*No defects found by VSA-QA. Test-runs 100% passed.

shiragoodman commented 3 years ago

hi @vhenry07 - we don't have any timeslots available on 4/2. Would Monday 4/5 at 3:30 pm ET work for you?

vhenry07 commented 3 years ago

Yes, that works for me. Veronica Henry | PMP Sr. Product Manager | mobile 702-509-6192 | e. @.***

On Tue, Mar 30, 2021 at 3:46 PM shiragoodman @.***> wrote:

hi @vhenry07 https://github.com/vhenry07 - we don't have any timeslots available on 4/2. Would Monday 4/5 at 3:30 pm ET work for you?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/department-of-veterans-affairs/va.gov-team/issues/22377#issuecomment-810531062, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASNVA6LJ4AIGMROTJFRZTOTTGITATANCNFSM42CRCGXA .

shiragoodman commented 3 years ago

@vhenry07 - scheduled for Monday 4/5 at 3:30 pm ET.

@Mottie - Ronnie said you'd be helping to supply the artifacts. Please provide the link to staging, as well as other artifacts requested, as soon as possible. We prefer to have these 4 days in advance of the review which would be today. Thank you!

Mottie commented 3 years ago

Hi @shiragoodman!

The link to the start of form 526 is https://staging.va.gov/disability/file-disability-claim-form-21-526ez/introduction

In addition to the artifacts linked above, here are:

wizard flow: https://staging.va.gov/disability/file-disability-claim-form-21-526ez/introduction
outline & alerts: https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/public-websites/how-to-apply-wizards/content-outlines/disability-form.md
IA review: https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/information-architecture/ia-reviews/websites-apply-wizard.md
Design (on info page, not intro page): https://vsateams.invisionapp.com/share/8GXOG91ZWNJ#/screens/421391044

shiragoodman commented 3 years ago

thank you @Mottie !

peggygannon commented 3 years ago

Hi, @Mottie @vhenry07 I have a couple of questions about the artifacts provided above.

Where should we review the wizard flow? The staging link shows the wizard on its own page, but the design mockup shows the wizard beginning on the static "How to file" page.

Where is the correct placement for the 526 wizard?

The "How to file" screen in the design mockup is different than the current "How to file" live page. (one example: they have different H1s) Does the mockup represent the new/updated "How to file: static page? If so, has this been reviewed by sitewide content team?

Mottie commented 3 years ago

The design is showing the wizard flow as it exists in production - rendered on the info page instead of the intro page. Once this review it done and successful, we will flip the feature flag so that the wizard appears as it does in staging.
The H1 between the design & implementation would be different because we're making the headers accessible. As for details about the mockup, I'll defer to @kevinstachura to answer that. He may not have the bandwidth to make modifications given that we are entirely focused on the NOD form now.

allison0034 commented 3 years ago

@vhenry07 @Mottie can you link the product outline? Right now it just links to your github folder with all the content.

vhenry07 commented 3 years ago

Product Outline:

ddzz commented 3 years ago

@vhenry07 Can you share links for your TestRail test cases and test execution logs?

vhenry07 commented 3 years ago

@ddzz I'm new to this role and just requested access to TestRail. Checking with my predecessor and QA lead to see if they can assist.

shiragoodman commented 3 years ago

the Staging Review has been cancelled for today, 4/5, and will be rescheduled for a later date. More info to come.

tlei123 commented 3 years ago

@ddzz , i hope to have QA-artifacts added here by late Wed. Will ping you on Slack when everything's ready.

cc @shiragoodman @pjhill

allison0034 commented 3 years ago

@vhenry07 there seems to be some confusion around what exactly has changed. Can you please let me know which screens I need to look at? Can you confirm that there were no changes to the actual 526 form? Thank you!

vhenry07 commented 3 years ago

@allison0034 - We are moving the wizard currently on the "How to apply and Eligibility page" to the /introduction page of the application. IA Review doc and Wizard flow linked above provide the details.

kevinstachura commented 3 years ago

Hey team - I believe we were tasked to retroactively make the switch to the new wizard format on 526 after we had already launched the BDD product, so that's why any designs you might see with the 526 gating are on the information page (how-to-file-claim/). We took the standard wizard format and took our (mostly) pre-existing content and fit it in the new wizard format.

@peggygannon - you and I worked on the language for all of the different options one sees when selecting 'yes' for the question 'are you on active duty right now?' and then entering their release from active duty date.

So we worked through the messaging the user sees based on the date. If I can find the ticket, I will link it here! It's from at least a few months back.

All in all, the ask is to have this page/wizard reviewed:

https://staging.va.gov/disability/file-disability-claim-form-21-526ez/introduction

And again, the design will not be 1:1 with staging since we did not formally mock it up - as it was (mostly) a content 'lift-n-shift' into the standard wizard design.

Please let me know if you have any further questions - thanks everyone!

tlei123 commented 3 years ago

@pjhill @ddzz , all QA test-runs completed, and QA-artifact links updated above in main description.

No defects; test-runs 100% passed.

cc @vhenry07 @shiragoodman

shiragoodman commented 3 years ago

@vhenry07 any updates on this?

vhenry07 commented 3 years ago

@shiragoodman We'll need to prioritize review of the 2 open tickets during next sprint.

shiragoodman commented 3 years ago

@vhenry07 ok no worries. Just didn't want it to fall off your radar. Please tag me here when you're ready :)

vhenry07 commented 3 years ago

@shiragoodman. All work completed. Link to wizard in staging updated above.

shiragoodman commented 3 years ago

@vhenry07 thanks! Would you update the Scheduling section with a new requested date/time so we can get this scheduled?

vhenry07 commented 3 years ago

@vhenry07 thanks! Would you update the Scheduling section with a new requested date/time so we can get this scheduled?

Yep, will do.

mnorthuis commented 3 years ago

@vhenry07 Have you coordinated with Sitewide content on content page and entry point changes? Can you link that ticket here?

vhenry07 commented 3 years ago

Link to sitewide content ticket.

department-of-veterans-affairs / va.gov-team