kellylein commented 1 year ago

Project Status Overview

Project Objective:

Implement a push notification strategy in order to proactively surface actionable content to Veterans and make it easier for them to complete tasks

Month	Project Health	Progress & Key Accomplishments
Jan 24	On track	Defining push notification uses cases in order to coordinate with external teams who need to provide data to VANotify and adding analytics to assess push notification effectiveness
Feb 24	On track	Use cases have been defined. VA Notify has created mass notification end point. Analytics (open rate and opt-in rate) for existing push notifications (secure messages & appointments) have been collected. Next step is meeting with POs to prioritize use cases and engage with external teams to get adding pushes for use cases on their roadmap.
Mar 24	On track	There are several different tracks being pursued for push notifications. 1. Existing push notifications, for secure messages and appointments, are undergoing content revisions to improve effectiveness. 2. A new push notification that informs Veterans that a new rx has been shipped will be implemented. Currently, the team needs to determine which backend teams to engage such that they can send data to VA Notify for this new notification. 3. A broadcast push notifications, that informs Veterans about new features like the home screen, are being explored. Currently, the opt-in flow to these types of push notifications is being explored. This opt-in flow will likely be used for new notification types added to the mobile app like rx or claims. 4. A new onboarding screen that explains how push notifications are used in the app has been designed and is ready to implement. This plan for the multiple push notification tracks is expected to be presented to POs in early April
Apr 24	On track	Plan was presented to POs detailing the following pieces of work. 1. Improve content for existing push notifications (Secure Messages & Appointments). This is contingent on whether Mobile can do this independently of Health teams. If not, this will be paused because Health teams are at full capacity. 2. Implement a broadcast push notification that informs Veterans of new features. This is currently paused until VA decides whether they are okay with these kinds of promotional push notifications 3. Designing and implementing an opt-in flow for new push notification types. 4. Implementing a push notification for Claims Decision Letter Available event, alongside the Event Bus team. 5. Implementing a context setting screen to onboarding that informs Veterans about how push notifications are used in the app.
5/21/24	On track	Opt-in flows have been created and need to be reviewed with POs. Plan to add Claims Decision Letter Available event has not been created and will be revisited once the Event Bus team is ready, likely in June
June '24	On track	No updates from the Event Bus team yet. Mobile team will be reaching out to them to understand requirements this month
6/26/24	On track	Mobile team confirmed that Event Bus' work to create claims decision letter available event is still in progress.
7/10/24	Blocked	Pending until Event Bus' work to create claims decision letter available event is complete.

Detailed Project Scope

Problem Statement

Assumptions

Risks

Definition of Done

Following needs to be true

|Item | Completed | |-------| ---------| | | | | | |

Project Scope

Items in and out of scope

|In Scope | Out of Scope| |-------| ---------| | | | | | |

Important Project Links

Links

- [Github](url) - [Product Brief](url) - [Product Canvas](url) - Design - [Discovery](url) - [Mockups](url) - [Final Design](url) - [Figma File](url) - Research - [Document 1](url) - [Document 2 ](url) -Analytics - [Document 1](url)

Team Members

Contact List

- **OCTO Product Leads:** Rachel Han and Ryan Thurlwell - **Ad Hoc PM:** - **Engineering:** - **Design:** - **External Team 1 & Role:** - **External Team 1 & Role:**

OKR and Analytic Metrics

Metrics

|What we are measuring | Why | Event Name |-------| ---------| ----- | | | | | | | | |

Checklist

Toggle Product Checklist

**Project Kickoff & Requirements Gathering** - [ ] Project Kickoff session - [ ] Initiative Scope finalized - [ ] Link Product Brief - [Sprint 0 ](https://docs.google.com/document/d/1WHDJ1iCt9J-acLx8_DSL4tkRKoVYqJGaRUqXuFf7ceg/edit# ) - [ ] Link to Implementation Strategy - Implementation Plan - UAT Plan - Release Plan - Metrics Identified (what metrics are we capturing, how do they tie into stakeholder OKRs, etc) **Pre-Production Readiness** - [ ] Associate Readiness - [ ] Update product guide - [ ] Coordinate with contact center support teams - [ ] What’s New Content - [ ] App Store/In App messaging (if applicable) - [ ] Coordinate with Release coordinator - [ ] App store Content changes required? Y/N - [ ] App store images needed? Y/N - [ ] QA Signed off - [ ] UAT complete - [ ] Obtain Go/No Go decision **Feature Go Live** - [ ] Ensure Waygate/Feature toggle release ticket submitted w/engineering & QA - **Template: Turn on Waygate/Turn off feature flag** - [ ] Coordinate with content & release coordinator if what’s new in app is required

Toggle Team Collaboration Checklist

- [ ] Design Intent & Feasibility discussions - [X] Research needed? No - [ ] UAT Needed? Yes/No - [ ] Ticket creation - [ ] Demo feature (mid check, end of development)

Toggle Design/UX Checklist

- [ ] Review problem/opportunity statement - [ ] Add questions and assumptions to product brief - [ ] Add research links to product brief - [ ] Document high-level research/design plans - [ ] Create lo/hi fi wireframes & user flows if applicable - [ ] Add links to Epic & applicable GitHub folders - [ ] Socialize designs - [ ] Sign off received - [ ] Complete Design QA - [ ] Does it require component review? - [ ] Accessibility review needed?

Toggle Content Checklist

- [ ] Review product brief and surface any questions, assumptions & risks - [ ] Participate in project discovery and kickoff activities/ceremonies - [ ] Complete comparative analysis/content research activities for net-new content - [ ] Review current content and determine where app may need to differ and potential improvements to share with web - [ ] Review past VA research and decisions documentation - [ ] Support Research & UX Design in research sessions and synthesis - [ ] Make content recommendations for lo-/hi-fi wireframes in collaboration with UX Design - [ ] Collaborate with Sitewide Content team for alignment, improvements, and sign-off - [ ] Participate in FE hand off - [ ] Complete content QA - [ ] Write copy for What's New In App - [ ] Write copy for app stores' What's New sections. - [ ] Write copy for updated screenshots in app stores

Toggle Engineering Checklist

- [ ] Are UI designs/ specs available/ready? If yes, they should be attached to attach specs. (We are assuming the design specs have been approved) - [ ] Are there any deadlines that need to be met? - [ ] What is the roll out plan? (Do we need a feature toggle? is this going to be available to every user immediately or do we want to roll out to a few users first) - [ ] Does this project require api integration? if yes, what api endpoint are we integrating with and what is the expected response body? - [ ] Do we want to capture analytics for this projects (i.e. update GA, add logs to grafana/datadog etc)?If yes, what metrics would we like to capture?

Toggle QA Checklist

- [ ] Create test plan - **Template: QA Test Plan** - [ ] Identify test data needs - [ ] Gotten & incorporated test plan review - [ ] QA Complete - [ ] Waygate tasks complete - [ ] Added new feature cases to the RC in TestRail - [ ] Added feature cases to appropriate section of active cases in TestRail - [ ] Spun up a (future) UI automation ticket for new feature

htcollier commented 3 months ago

See Push Notification Opt-In #9124 epic for implementation.

davidconlon commented 2 months ago

@rachelhanster Is this still under mobile or should it be with VANotify or a Benefits Experience team? Regardless the dates of this effort should be updated.

rachelhanster commented 2 months ago

@davidconlon: Neither team. Mobile team needs to revisit this epic, in concert with other, concurrent push notifications epics.
My recommendation is to archive this epic #6038, use other existing notifications-related epics, and each Experience Team/portfolio (?) create new ones targeting smaller, scoped problems. All 3 OCTO portfolios have work to do on push notifications; each push notification will likely need investment in backend service/endpoint(s) creation or updates. Experience Teams in each portfolio can then decide if/when they interact with VANotify, a shared service.
I'll let @rtwell and @ajsarkar28 decide.

davidconlon commented 2 weeks ago

Per discussion with @rtwell closing in place of https://github.com/department-of-veterans-affairs/vanotify-team/issues/1421

department-of-veterans-affairs / va-mobile-app

Push Notifications Strategy #6038