RX Refill Post-MVP

[b-rocha]

Epic Status Overview

Problem Statement:

High level description of the epic and the problem we are trying to solve

Why is this Important?:

Definition of Done:

What set of criteria must be met for this epic to be considered complete?

Success Criteria:

What measurable outcomes will be used to indicate that this epic has successfully delivered value (i.e. - what is the impact)?

Product Brief:

• [link to GitHub Product Brief]

Monthly Update for Stakeholders

Date	Progress & Key Accomplishments	Issues/Risks/Blockers
MM/DD/YY
MM/DD/YY
MM/DD/YY
MM/DD/YY

VA Stakeholders

Reference Links

List links related to epics, pitch deck, one pager, product folder, etc.

[bischoffa]

@ala-yna not sure where this sets as the RX MVP was already launched. Seems like a lot of follow-up improvements not sure if they are still relevant.

[BeccaTupaj]

@b-rocha This is an epic of Rx Refill post MVP updates. What are your thoughts on keeping this in our backlog vs closing? If we decide to keep it, then I want to write this up using our epic template, and I would want to make sure that each sub issue is written as a user story.

I think we should ask Ryan about the priority of this work since I don't know who initiated all of these tickets.
cc: @rtwell

[BeccaTupaj]

Next Steps with this epic:

1. In Sprint 4 assign epic to Kira to review issues and assess what work is specific to the mobile version of this feature and should be prioritized. (Ensure that each issue we are keeping is written up as a full user story with AC. Becca or Brenda will write up, once we know which ones we are keeping.)
2. Hand off those prioritized user stories to the Rx Refill Experience Team as our recommendations for what should be fixed in the app.
3. Either the Experience Team will make those fixes and hand back to use for PR and QA, or we will help with making those fixes.
   cc: @b-rocha @rtwell