Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DRAFT Sprint 3 Plan - Facilities #17895

Closed
davidmpickett opened this issue Apr 18, 2024 · 7 comments
Closed

DRAFT Sprint 3 Plan - Facilities #17895

davidmpickett opened this issue Apr 18, 2024 · 7 comments
Labels
Facilities Facilities products (VAMC, Vet Center, etc) sitewide

Comments

@davidmpickett
Copy link
Contributor

davidmpickett commented Apr 18, 2024

Schedule Notes

Sprint 3 = 5/1 - 5/14

  • Michelle OOO Wed 4/24-Fri 5/3
  • Christian: OOO Drupalcon, week of 5/6
  • Eli OOO: Th 5/9
  • OCTO offsite: 5/8-5/9 + travel days (5/7, 5/10) for DaveC, Michelle, Amanda

FYSA: DaveC PTO this week; Chris Kim on leave for May; Josh Mills backfill

Sprint Priorities 🎯

At the end of this sprint, what do we want to have accomplished/delivered?

CY Q2 Priorities

Numbered list
  1. Fac: Update existing V1 components to use Web Design System v3 #17653
  2. [Facilities] Migrate off of font-awesome for iconography #17722
  3. department-of-veterans-affairs/va-iir/issues/553
  4. SE: Lighthouse V1 adoption before V0 EOL #14507
    4a. Update Vets-API Facilities API to use Lighthouse v1 (Phase 1)  #15344
    4b. Facility Locator uses Lighthouse API v1 with existing functionality (Phase 2) #12907
  5. Launch plan for VBA/VAMC Service Locations enhancements #16825
  6. VBA Regional Offices Pilot MVP #10514
    6b. VBA RO Pilot Staging Review #16268
  7. Link to Health chat from VAMC pages #15037
  8. Facility Locator iteration: Provider core training / PPMS data #14225
  9. Fac: Adopt V1 & V3 components to replace custom code implementations  #17655
  10. Remove inline entity form (IEF) from Vet Center services #17708
    10b. Improve error experience for Allow Only One #7818
  11. [SUPER EPIC] Vet Center design 2.0 #17661
  12. Removed
  13. Initiative - VAMC Mobile Clinic  #12923
  14. VBA Regional Offices: MVP National Rollout #14477
  15. Removed
  16. Supporting MHV on VA.gov from VAMC pages  #12942
  17. [EPIC] VA Police Transparency MVP #14327
  18. [EPIC] Facility Locator: AutoSuggest for "Service type" #15541
  19. Removed
  20. Improve services accordions and service locations across Facilities products #17350

Non-quarterly prio injections

2) va-icon adoption - end of May deadline - #17722

3) Security / PII issue (IIR) - https://github.com/department-of-veterans-affairs/va-iir/issues/553

  • FE - May need some capacity to review work done by IIR

4) Lighthouse v1 (IIR) - #14507

5) VBA/VAMC Service Location enhancements - #16825?

Not Launch Blocking

6) VBA Staging review blockers - #16268

6b) VBA Pilot MVP: other launch-related - #10514

8) Facility Locator iteration: Provider core training / PPMS data - #14225

9) Adopt V1 & V3 components to replace custom code implementations #17655

10) Vet Centers remove IEF - #17708

11) Initiative - Vet Center design 2.0 #17661

Child epic: Veterans can distinguish Vet Centers from VA medical facilities #17893

18) Facility Locator: "Service type" field iterations #15541

20) Improve services accordions & locations across products - #17350

Other Work (Not Q2 Prioritized)

Sprint 4 Holding spot

Priority updates

7) Link to Health chat from VAMC pages - #15037

Paused due to VHA DM communications planning.

@davidmpickett davidmpickett added the Facilities Facilities products (VAMC, Vet Center, etc) label Apr 18, 2024
@jilladams jilladams added the Epic Issue type label Apr 19, 2024
@jilladams jilladams changed the title DRAFT Sprint 3 Plan - Facilities DRAFT Sprint 3 Plan - Facilities 17895 Apr 19, 2024
@jilladams
Copy link
Contributor

jilladams commented Apr 19, 2024

  • Updated PTO from cal as of today
  • Added Sprint 3 tickets to epic
  • Updated list of initiatives / tentative tickets in sprint, based on top-down Q2 prios + injections

TO DO prior to planning:

  • Remove Sprint 2 tickets that have closed
  • Cross walk Ready column for any high priority items that get refined and are not included
  • Double check load:
  • Review with Michelle Amanda
    • Update changes from review

@jilladams
Copy link
Contributor

Note to selves: @laflannery is scheduled for a Service Locations demo to VAMC editors on 5/8. We need to flag if that will not work, at the beginning of this sprint.

@mmiddaugh
Copy link
Contributor

@jilladams @davidmpickett
Under Non-quarterly prio injections, I see the suggestion to do #17646 and #17649 before #17547 but I'd suggest starting with a query to confirm if the provider is in the data set rec'd in response. This would allow us to give feedback to the PPMS team if that's the issue. I've located the provider on a completely separate map and then zoomed into the same area on the FL and the provider is not in the results list. I'm not sure pagination is in play here.

@davidmpickett
Copy link
Contributor Author

@jilladams @davidmpickett Under Non-quarterly prio injections, I see the suggestion to do #17646 and #17649 before #17547 but I'd suggest starting with a query to confirm if the provider is in the data set rec'd in response. This would allow us to give feedback to the PPMS team if that's the issue. I've located the provider on a completely separate map and then zoomed into the same area on the FL and the provider is not in the results list. I'm not sure pagination is in play here.

I confirmed that this is not pagination related. Pulled 17547 up to discuss at top of Team Refinement tomorrow

@davidmpickett davidmpickett changed the title DRAFT Sprint 3 Plan - Facilities 17895 DRAFT Sprint 3 Plan - Facilities Apr 26, 2024
@davidmpickett
Copy link
Contributor Author

@jilladams to confirm what I think you said in demo today. 2) va-icon adoption is partially blocked by DST, so we should prioritize FE tickets from 9) Adopt V1 & V3 components instead?

@davidmpickett
Copy link
Contributor Author

@jilladams Also I just updated the ticket body to include tickets that seem likely to roll over from S2 given current state

@jilladams
Copy link
Contributor

From planning:

  • We will hold on DS icon work until the alignment / padding work is fixed on the component. Main idea here is that it's not worth double review if we do the work now and merge to an integration branch that must be checked again when we merge.
  • Noting: With DS deadline changes, we may want to review our priorities in order to help plan next few sprints. @jilladams or @davidmpickett to bring this to product sync.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Facilities Facilities products (VAMC, Vet Center, etc) sitewide
Projects
None yet
Development

No branches or pull requests

3 participants