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/
10 stars 1 forks source link

Travel Pay - Submit Travel Reimbursement Claim from Claims Feature #6604

Open bischoffa opened 10 months ago

bischoffa commented 10 months ago

Project Status Overview

Project Objective:

Acceptance Criteria:

  1. User navigates to Benefits/Claims and sees option to start a travel claim
  2. For an eligible appointment, user sees option to start a travel claim
    • Eligible appointment = Veteran is Checked-In and appointment date is < 30 days old
  3. User sees messages on tasks to do before submitting a claim and getting reimbursed. User is redirected to do these tasks
  4. For users who have already successfully submitted a claim and got reimbursed, do not show message(s) in step 3
  5. User submits a claims
  6. User tracks claim

Current Dependencies / Blockers

Blockers |Blocker | Team / Owner | Est to Resolution | |-------|---------|-------| | | | | | | | | |

Project Timeline

Milestones |Step | Timing | |-------| ---------| |Sprint 0 - Discovery | | |Step 1 - Strategy | | |Step 2 - Design | | |Step 3 - Building / Implementing | | | 100% Release | | |Step 4 - Post Verification| |

Monthly Update

Updates |Month| Project Health | Progress & Key Accomplishments| Issues/Risks/Blockers| |-------| ---------|--------|---------| |Aug '23| Not started | Decided to pull this out of the epic 1255 and to create this epic as a phase 2 of it. Agreed upon by Rachel PO on 8/28| | |Sep '23| Not started | No changes, not prioritized | Prioritization | |Oct '23| Not started | No changes, not prioritized | Prioritization |

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 - **PM:** Rachel Han - **Ad Hoc PM:** Meko Hong - **Engineering:** Jayson Perkins and Jon Bindbeutel - **Design:** Lauren Russell - **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
bischoffa commented 10 months ago

Items removed from epic 1255 and moved to here

Test B:

  1. User navigates to Benefits/Claims and sees option to start a travel claim
  2. same as A, step 2
  3. same as A, step 3
  4. same as A, step 4
  5. same as A, step 5
  6. Same as A, step 6

Veteran give to and get money from VA:

Same for A and B:

  1. User navigates to Payments (only tracked on BTSSS as of now)
  2. User sees travel co-pay(s) and reimbursement(s) (only tracked on BTSSS as of now)

Veteran checks status. 2 paths:

  1. Appointment/Past/Confirmed appointment
  2. Benefits/Claims

This feature will also encompass work in order to do comparison between Appointment Travel Claim feature and Claim's Travel Claim Submission feature.