Sprint 31 priorities for Product Support Team

[kevwalsh]

🥅 — Sprint goals (pending Sprint planning)
👥 — Needs discussion, meetings and/or refining

Context

1. This remains the Product support team but in Sprint 31 we're going to start feeling the shift in priority towards Accelerated publishing
2. This will take product support team engineer and design energy from Product development. Ethan will be jumping into the discovery effort net sprint.
3. This scrum team has taken on some critical Core initiatives and responsibilities, specifically help desk, CMS design system, and user admin, and all of which dilutes our focus a bit. Kaise in particular will start
4. We are also going to be needed to contribute to the Drupal 9 upgrade

What will not change

1. Customer service and change management initiatives (help desk, training, etc)
2. Ongoing support for Product epics already in progress (Vet Center, VAMC Policies Page, CLP)
3. Maintenance and Tier 2 support for products (Tier 2)

#1950 Drupal 9 upgrade

- [ ] #4944 Mob testing session - deprioritized by Core team

#4019 User administration service

• Design Improved Role delegation UI  #4997 Design Improved Role delegation UI
• Improved "Section" UI in PR environment and get feedback #5088 Improve Section UI in PR environment and get feedback

Public Websites

Agenda for weekly sync with Public Websites team

CLP

#4989 Replace "Audience (tags)" open-ended field with a reference to two existing audience vocabularies 🥅

Not in sprint: CLP request form

Facilities

Agenda for weekly sync with Facilities team

Vet Center

#4374 Local editor experience

• Bug fixes to forms and governance, if any.
• Vet Center dashboard edit links are missing the destination paramater #5110 Vet Center dashboard edit links are missing the destination parameter
• Include current page in breadcrumbs for Sections #5089 Include current page in breadcrumbs on all section taxonomy pages

#4400 Change management for local editors 👥

• Finalize Vet Center training materials #5133 Finalize Vet Center training materials and user guides

#4373 National editor experience

Centralized content editorial experience has been deprioritized.

VAMC System

• VAMC launch support for 8-10 VAMCs #5134 Launch 8-10 VAMCs @swirtSJW @kevwalsh

Policies Page

• Provide tools to analyze top task page revision histories #5099 Tools to analyze top task page revision histories
• Create runbook with VAMC upgrade team for for VAMC System Policy Pages #5053 Collaborate with VAMC upgrade team on VAMC System Policies page runbook and launch one Policies page 🥅
  • Write Release note that could be sent by VHA Digital Comms about this change, including link to training.

#2427 Epic: Enforce IA design for VAMC editors**

• Finish implementation Implement VAMC menu governance #4988 / PR VAGOV-4988: Menu governance for VAMC product. #4894 🥅
• Change management for new VAMC menu settings (IA hardening)  #5135 Change management for new IA / menu governance
• Collaborate with IA team on VA Pittsburgh IA issues #5132 Collaborate with VAMC upgrade team, Facilities team on Pittsburgh IA changes

Stretch

• Document how to update URLs for content admins for VAMC product 👥
• How to make the CMS force the correct URLs for VAMCs for new pages 👥
  • Change pathauto for Detail Pages to use the full menu hierarchy. #4773 Update pathauto for Detail pages to use [VAMC system homepage]/[menu-hierarchy]/[h1]
• Programatically re-align dual-state sites to the correct IA 👥

Help desk

• Broken link analysis - Editor vs CMS vs Front end template vs Front end build issues.
• VAMC help request analysis

Lighthouse collaboration

Link to agenda

• If a Vet Center or VAMC staff finds an issue with the data coming through Facilities API, what should they do? Multiple data sets... Access to care, Mental health care contacts, VAST.