Share POC with OPO/CS

[mackhowell-nava]

Issue Description

• If we do not get the chance/confirmation from DBEX that their 0781 launch in late march is still feasible, then this would be a great milestone for us to round out Q1.

• Getting our desired changes/POC approved by OPO/CS (via Alejandro) will further help to validate this project going into Q2 2025.

• Notes from 2/26/25 EE team sync

  • "We need to put together a small story for them here."
  • The POC/demo here can be a generated PDF(s), with mock data, from staging code, based on our designs.

• Notes from 2/13/25 EE/OBA sync

  • Should it be a phased rollout? Or tested at a single RO?
  • Alejandro: Based on past practices – would recommend a phased rollout. Starting at 1% level.
    • But during the period of that first rollout, would want eyes. Validate what it’s looking like. Also have enlisted OBI (sister team) to do manual review. As well as doing ad-hoc touchpoints to do a case by case review of some sort of sample size.
    • We typically look at 20-30 of them per phase, and then go from there to increase %.
    • Alejadro and all colleagues all have VSR experience, it’s not such a significant feature to warrant that.
    • He could invite several colleagues from his team to get qualitative input.
  • Shannon – we don’t need to bring on anyone from VBA for approval?
    • We want to run this by OFO (OPO?), and include CS.
    • Alejandro can get names, and bless what we’re doing before we launch to that 1%.
      • We DO need stakeholders involved before we do that 1% rollout.
    • When is the right time? (we’re doing POC development right now)
      • Alejandro thinks it would be when we have the expected version in hand to show them. So we don’t have to go back to them later with updates/changes.
      • Based on the momentum that exists now (with dept. changes) – Alejandro will get this approval process started (and get names)
      • He’ll send them the POC screenshots, once it’s ready.
      • “This is what we’re looking at, would you like to discuss more?” Do they have any issues at face value?

---

Tasks

• The team aligns on the POC that we're sharing with OPO/CS, and ensure what we generate is feasible (see Review design updates to 0781 with engineering #4157)
• We generate "before" and "after" samples to share with Alejandro
• The "after" PDF is generated from real code that we've written in vets-api
• Check with Jen/Shannon that we've provided enough to tell the story here

Acceptance Criteria

• Alejandro has the POC/assets he needs to share our progress with OPO/CS and get their blessing to proceed.

---

How to configure this issue

• Attached to an Epic (what body of work is this a part of?)
• Labeled with Practice Area (engineer, data science, design, research , product)
• Labeled with Type (bug, request, discovery, documentation, etc.)