search

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

"If VA were a company, it would have a flagship mobile app."
https://department-of-veterans-affairs.github.io/va-mobile-app/
16 stars 2 forks source link

Appt List & Details content alignment - Online / Video (Virtual) #7313

Closed bischoffa closed 5 months ago

bischoffa commented 11 months ago

Project Status Overview

During the Appointments V2 integration, we noticed some inconsistencies on how we (mobile) display or do not display information on the appointment list/detail views. Some highlights, to name a few

Phone and In-Person were worked and completed within Epic 5135

Veteran Pain Points

  1. Missing and confusing appointment information makes the list difficult for Veterans to prepare for their appointments
  2. In past research studies, Veterans expressed that missing and or inconsistent appointment details such as type of care, clinic name, physical location, and provider information make it difficult for them to understand their appointments.

Current Dependencies / Blockers

Blockers |Blocker | Team / Owner | Est to Resolution | |-------|---------|-------| | Product owner of Appointments are making changes to video appointments, thus identified by Mobile POs to do In-Person vs Video changes in the app. Will need Mobile POs to coordinate with VA Appt Team to determine readiness | External VA Appt Team & Mobile PO | | | | | | |

Project Timeline

Milestones |Step | Timing | |-------| ---------| | Step 1 - Video - strategize / research | Not yet prioritized | | Step 2 - Video - define recommendations and draft tickets | Not yet prioritized | | Step 3 - Video - implement changes | Not yet prioritized |

Monthly Update

Updates |Month| Project Health | Progress & Key Accomplishments| Issues/Risks/Blockers| |-------| ---------|--------|---------| |July '23| |Aug '23| ..... |Sep '23| |Oct '23|

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 - [Product Brief](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/va-mobile-app/features/appointments/product/AppointmentListEnhancements/AppointmentListEnhancement_ProductBrief.md) - [Decsion Log](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/va-mobile-app/features/appointments/product/AppointmentListEnhancements/decisionlog.md) - [Figma Mapping](https://www.figma.com/file/k0Ny9KoP1prsI7o661Tyf3/%F0%9F%94%8D-Appointments-Content-Inventory-2.0---Working---VAMobile?type=whiteboard&node-id=0-1&t=OtdNGFckhpKwZsKm-0)

Team Members

# Supporting Team
| Name | Role | | :--------- | :--------| | Rachel Han | Product Owner, VA | |Ryan Thurlwell | Design Lead, VA | | | Sr. Product Manager, Ad Hoc| | | Sr. Content Designer, Ad Hoc| | | Sr. UX Designer, Ad Hoc|
### OKR and Analytic Metrics
Metrics |What we are measuring | Why | Event Name |-------| ---------| ----- | | | | | | | | |
### Questions
Open Questions
Closed Questions | Question | Answer | |--------|----------| | | | | | |
### Change / Decision Log Product will need to create on in the Github folder and link it here. # 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? - [ ] Do we need to update our in-app review code to include this new feature?
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
bischoffa commented 9 months ago

May need to revisit when Community Care appointments get updated as there are 4 types

  1. In Person - 12/21/23 release
  2. Phone - completed 1/16/24 release
  3. Virtual - this epic
  4. Community Cards - not sure there is an epic yet
ala-yna commented 5 months ago

Closing this epic - this work will be tracked in Improvements to Appointments and Alignment with Web #8193