PW Sprint 82 plan

[jilladams]

Q2 Priorities

Items with [x] are carried over from previous sprint

1. Income Limits web app #9626

Design / Research:

• IncLim: Conduct User Research sessions #12976 (8) - Research
• IncLim: User research synthesis #11101 (13) - Research
• (stretch) Income limits: visualize post-research recommendations (as needed) to aid discussion with stakeholders #11102 () - Design

Engineering:

• Discovery: document architecture and data-load approach for non-VES database solution #13189 (5) - BE
• (Eric Oliver dependency ~2hrs) Verify vets-api connection to VES database & define next steps #12348 (5) - BE

2. Benefit Content Model Hardening #9628

• VA Benefits Taxonomy Build Ph3: CMS Collab cycle #13074 (5) - BE
• VA Benefits Taxonomy Build Ph4: Complete and merge #13075 (5) - BE
• VA Benefits Taxonomy: enforce no self references for taxonomy references and final field requirements #13206 (3) - BE
• VA Benefits Taxonomy Build: Prevent duplicate taxonomy terms #13231 (3) - BE

Post-MVP

• Add workflow functionality to VA Benefit Taxonomy #13141 (8) - BE
• (stretch) VA Benefits Taxonomy: Explore Chosen to implement better a multi-select interface #13232 (needsrefined) - BE
• (stretch) [Benefits Taxonomy] Enable translation for MVP fields #13207 (needsrefined) - BE

3. PACT Act Wizard #12170

First ticket is ready for Cindy (research)

@wesrowe TODO: Initial convo in S82, 1hr, Jordan, Wes, DanielleT, Cindy(?), DaveC optional to determine: are the flow chart paths we're creating are the best way. And: best way to map it for testing, given deeper complexity than Discharge wizard.

• (stretch) PACT wizard: User Research and Collab Cycle planning #13233

4. Expand Q&A Reusability #10780

Not yet prioritized:

• SPIKE: Remove in-line editing of reusable Q&A from FAQ & R&S content type #13221 (3) - BE
• (stretch) Implementation: Remove in-line editing of reusable Q&A from FAQ & R&S Detail content type #13220 (needs refining) - BE
• BE: Document the process to expose Q&A on new content types #10936 (3) - BE
• FE: Document the process to expose Q&A on new content type, once added in CMS #10937 (needs refining) - FE

5. Public WebsitesUS Design System 3.0 #12995

Updating any design system components to be compliant with USWDS 3.0, downstream from VA Design System work. Not yet actionable. (DST building their Ph1 (sample form) in Q2.)

• Migrate "phase 2" react components targed for deprecation: es-lint & other #13135 (5) - FE - may need broken up into multiple tickets / sprint sized
• Migrate "phase 2" react components targed for deprecation: migration script set #13175 (5) - FE

Other Q2 priorities not in motion

• Translation in R&S, Hubs [EPIC] Translation: Build dynamic translation capability into Benefit Hub & R&S pages #12996 – FE templating to make CMS-entered translations visible. Possible dependencies on BCM hardening and fast publishing (because translation is field-by-field).
• Public Websites supporting MHV on VA.gov – Update the secure messaging widget to point to MHVonVAgov rather than Cerner / VistA. Not yet actionable. Sitewide Content input: There will also be content tweaks within the widget. Timing unknown but won't be sudden.
• Header/footer redesign - Awaiting info / green light for kickoff

Q1 Finish-up

Post-MVP Homepage #11170

• (stretch) Homepage modal: show modal to 100% of users, deprecate local storage mechanism for controlling rollout #12162

Cerner API deprecation support

• Support/monitor Cerner data addition by a Health team #13200 () - FE
• (BLOCKED) Remove "Hard-coded API" from codebase #9307 (5) - 9307 remove hardcoded cerner api vets-website#23036 (comment) - FE

Other PW Priorities

Forms monitoring/errors:

• Establish monitoring of nightly Find-a-form Sidekiq jobs #13216 () - BE
• Forms API: improve nightly update job to leave data in previous day's state if interrupted #13241 () - BE
• Discovery: DataDog logging and alerts for Forms monitoring - API level, e2e test in Prod, etc #12978 () - BE

Other priorities

• NEW TICKET: Debug source of Yellow ribbon data problem from emails
• (stretch) Discovery: downtime alerts (existing feature) #12339 (5) - FE
• (stretch) Discovery: Yellow Ribbon search tool implementation and health monitoring #13084 (needs refining) - FE/BE
• (stretch) Write script for creating event data and implement unit tests #12932 (8) - FE (Daniel)

Content / IA priorities

• Redirect Request: Flu Campaign landing pages - no hard timing #13186

Epic of upcoming redirects not yet in our board:
Team repo #53921

Tech debt & Defects

• (carryover from s78) Events list: Events in progress do not appear as Past or Upcoming #10307 (~5? remain) - FE
• (carryover from s80) Fix: VA forms are incorrectly showing up in VBA and VACO sections #12933 (5) - BE
• (stretch) Design: Provide address in "Where" field for all Events at VA facilities instead of linking to facility's web page #13124 () - UX Design
• (stretch) Multiple instances of the same Reusable Q&A on the same page results in a duplicate ID (508-4) #11448 (5) - FE

User research and UX pipeline development

• (stretch) Analyze Medallia qualitative survey data for remaining PW portfolio products #12791 (8) - Research
• (stretch) Iterate portfolio analysis for research plan pipeline #12601 (5) - Research
• (stretch) UX: comparative study of search and filter UI across PW products #12719 (5) - Research

[jilladams]

• Benefits: need to schedule Collab cycle review of build after Phase 2 is done
• Benefits: need to create ticket for 508 review of CMS UI after Laura PTO
• Benefits CMS Design: need to consider / plan for user review with Content IA team
• Benefits: decision log, add the decision around modifying the Official Benefit Name after initial creation
• Benefits: Need a ticket to get the CMS content model spec tool updated - [Benefits Taxonomy] Create Content Model documentation in Drupal for the final VA Benefits taxonomy product #12829
  • Need to get info from Swirt re: how it works

[wesrowe]

• add PACT wizard: User Research and Collab Cycle planning #13233 in place of todo
• add Discovery: DataDog logging and alerts for Forms monitoring - API level, e2e test in Prod, etc #12978 as first DataDog issue (updated it to include sidekiq if appropriate)