Epic: VA Notify: Moving This Team into Platform

[jknipes]

Status

Update each sprint until completed	Date	Status	Launch Date (see above)	Notes
11/6/24	PAUSED	7/26/24 off-track	Paused per Dave Conlon to Feb 2025
10/21/24	PAUSED	7/26/24 off-track	Paused per Dave Conlon to Feb 2025

Product Outline

Link

High Level User Story/ies

As a VA Notify team member, I need a public location for my team's documentation, so I can know where to direct users of our tools.

As a VFS team member, I need to know where I can access documentation about VA Notify, so I can know how to use their tools to help Veterans.

Hypothesis or Bet

If we migrate VA Notify documentation to Platform Website then we expect more traffic to the website from VFS teams and higher satisfaction overall.

OKR

info for all common VFS needs are findable in a Platform Website

Definition of done

• [ ] All issues in this epic are complete, and VA Notify Team is able to view, edit, and upload their documentation on Platform Website.

Artifacts

Adding VA Notify to Platform What the Content Team Needs to Know VA Notify on GitHub

Take into consideration Accessibility/QA needs as well as Product, Technical, and Design requirements.

How to configure this issue

• [ ] Labeled with Team (product support, analytics-insights, operations, Console-Services, tools-fe,content-ia, service-design, vsa-*)
• [ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)

[jknipes]

work is being deprioritized for Content team while waiting for VA Notify to reach alignment with the new POs. PM, Melanie Jones said she informed Platform program manager about this as well