VBA RO Pilot Staging Review

[xiongjaneg]

User Story or Problem Statement

Staging review for VBA Regional Office Pilot MVP is scheduled for March 21. This is to prep any materials in advance by 5 days prior (longer due to using Tugboat).

This is for product and content artifacts. QA artifacts are covered in #17318

Per Shira in Slack:
Please be very clear within the Staging Review artifacts section what the scope of work is and which pages should be included for review. Not knowing this information can increase the amount of time we spend reviewing, and can lead to us reviewing pages outside of the scope of the changes the VFS team is making. I imagine this could also be a challenge with a new tool.

Imposter components

Amanda verified with Matt Dingee that current Spotlight pattern will not be a blocker for staging review, but we should continue to replace it with a va-card component.

Imposter Components and V1 Design System Components will be flagged at Staging Reviews
Starting March 18th, 2024, Governance Team will flag as violations of the VA.gov Experience Standards any imposter components in VFS products. An imposter component is one that emulates the look and function of a Design System web component. In addition, Governance Team will flag the use of most V1 Design System components.

Impact: VFS teams should replace imposter components with the corresponding Design System web component absent a legitimate technical reason why the Design System web component is inadequate. V1 components should be replaced with the V3 counterpart if it exists.

Documentation

Prerequisites / Blocking issues

• Update VBA template to display "Manage your benefits online" #17598
• Only published VBA services should display on front end #17599
• "Schedule an appointment online" line on VBA Facility Services should point to VERA #17710
• SPIKE: Document the state of VBA Regional Office testing and prep for Staging Review #15223
• VBA: Perform Foundational testing of the FE for Staging Review #16369
• Establish and enact VBA facility alias pattern #15155
• VBA RO Bug bash #18159
• SPIKE: VBA not correctly referencing Drupal Appointment introduction text values on FE #17999

Not launch blocking, but good to fix

Moved to parent epic - #10514

Artifact prep

Required artifacts are linked in the collab cycle ticket

• Product artifacts
  • Staging URL - N/A, we are going to provide a Tugboat
  • Tugboat URL
  • Specify which pages are included in the review
  • Staging test user information - N/A, unauthed experience
• Content artifacts
  • Please include a link to any Sitewide CAIA feedback you received, including a content source of truth, any relevant static content page and entry point updates, and the intake form.
• IA artifacts
  • Please include a link to any Sitewide CAIA feedback you received, including an IA review document or intake form.
• QA artifacts
  • An artifact that corresponds to each standard in the QA Standards. (Created by Eli, but not linked yet in Collab Cycle ticket yet)
• Accessibility artifacts
  • Completed accessibility testing artifact. For details, see Prepare for an accessibility staging review.

[xiongjaneg]

Please add your planning poker estimate with Zenhub @davidmpickett

[xiongjaneg]

@davidmpickett We'll just count points you've timeboxed to do work on this (primarily content and IA artifacts). Thank you!

[davidmpickett]

IA artifacts added

[davidmpickett]

Content Artifacts section added as well. @xiongjaneg let me know if there's anything else I can do to support you on this

[xiongjaneg]

@davidmpickett You are the awesomest. Thank you!

[xiongjaneg]

Staging review postponed, moving issue to backlog for when review is rescheduled

[davidmpickett]

Adding #17095 as a blocker since imposter components will no longer pass staging review.

[mmiddaugh]

I'm not sure "Additional Hours Options" content shows in Italics #17686 should be considered launch blocking since it's the existing behavior on VAMC pages in Prod (although we do need to fix it)

[jilladams]

@davidmpickett to line up approach, I converted this to an epic and pulled the blocking issues into this epic, so it acts like the Service Locations launch plan.

[mmiddaugh]

@davidmpickett if at all possible, we should improve the editor UX slightly by adding more support via navigation to the VBA Facility Service workflow from the VBA facility node before staging review

• i.e., Replace "Facility services are created on a different page." with "Add or edit Facility services [here](VBA service link)"

[davidmpickett]

@davidmpickett if at all possible, we should improve the editor UX slightly by adding more support via navigation to the VBA Facility Service workflow from the VBA facility node before staging review

• i.e., Replace "Facility services are created on a different page." with "Add or edit Facility services [here](VBA service link)"

Ticket stubbed and noted as not launch blocking, but good to fix and queued for Refinement #17885

[jilladams]

@davidmpickett Can we move "Not launch blocking" list out of this epic into the parent Pilot epic?

[davidmpickett]

@davidmpickett Can we move "Not launch blocking" list out of this epic into the parent Pilot epic?

Great idea. I'll move those now

[davidmpickett]

@Agile6MSkinner @jilladams @mmiddaugh I'm closing this Epic since it reflected the work to get TO Staging Review. Any work that comes FROM Staging Review tomorrow can sit in the Pilot Epic