VBA Regional Offices Pilot MVP

[davidmpickett]

Background

Capturing the larger tasks and their rough order of operations to complete VBA MVP

Edit: 10/30/23 Sub-epic tickets for Pilot MVP moved under this epic for current state status clarity

User Story or Problem Statement

As a Sitewide Facilities team member, I want to see the plan for executing tasks for completing MVP.

Definition of Done for MVP

• 7 MVP ROs are entering content into Drupal and at least 1 site has entered Dual-State
• Feedback from MVP rollout is gathered and synthesized into actionable tickets for Fast Follow phase & National rollout

High level flows

VA.gov Front End Pipeline

FE design and build governed by Platform Collab Cycle

---

Drupal CMS Pipeline

CMS design and build governed by CMS Collab Cycle

---

Service Taxonomy Pipeline

VA Service Taxonomy work governed by CAIA & Taxonomy Council

[EWashb]

@dawnpruitt I suggest getting this epic refined before starting the work on the ticket. It seems pretty blank right now and I just want to watch out for what the intention of this work is, the scope, and what our definition of done is :)

[jilladams]

7/20 team refinement: notes from today, @mmiddaugh @davidmpickett @swirtSJW @omahane @maxx1128 @eselkin @thejordanwood @cindymerrill @ALogsdon3

Organization

• VBA Regional Offices modernization #13029 is a parent to this MVP effort
• Any non-MVP tickets / epics can move to VBA Regional Offices: MVP National Rollout #14477
  • TODO:
• Any MVP issues / Tickets need to live under here, preferably organized into chunks of work that can be mapped as a gantt. Epics that exist today (TODO: add #s):
  • Remaining Spec work
  • FE design
  • FE research
  • CMS design
  • CMS research (tbd, decisions)
  • Dev work:
    • TODO: We need to break this up into logical chunks (CMS vs. FE? Editor- vs. Veteran-facing?)

All VBA tickets by search VBA term (not foolproof): #14436 (comment)

MVP: how to ship something Editor or Veteran facing faster

We are at the 1 year mark of the project. Delays are inevitable. Still: we cannot wait another year to ship something.
“How small is the M in MVP?” How could we break up delivery?

BIG PICTURE DEPENDENCIES

• Finalize content specs
  • CMS: Build skeleton content types
• Design of CMS UX
  • FE: Template FE
• Hook up FE to CMS data

Some options for shipping:

1. SANDY'S DB: make the data Veteran facing

• Create FE templates for data coming from Sandy’s DB (address, name, hours, operating status).
  • Would act like a Facility Locator detail page
  • Doesn’t inherently seem valuable

2. Break up bigger delivery

• Design analysis at Midpoint: Evaluate: Which portions of design are A) stable / build-ready, vs. B) Will be assessed/ affected by usability testing? For stable portions, evaluate opp to start build.
• Could parallelize

3. Start research earlier - already doing this
   • Option: Could we kickoff research before content is complete?
     • Focus content efforts on the content needed for specific research tasks. -- this is already done this way
     • Figure out the design for an open accordion. -- underway

NEXT STEPS:

• UX Refinement

  • Can Alexis help with Specs? She's willing.
  • Review plans for Editor research. Necessary? How can we move it faster?

• FE & Drupal refinement:

  • look over existing tickets
  • Break into logical epics
  • Figure out what can be parallelized / dependencies.

• Permissions

  • SPIKE ticket: prove we can add a 2nd workflow without breaking things, in order to persuade CMS Team
    • Blocking permissions proposal.
  • Permissions proposal: (TODO: link Kamari's doc) Revive, refresh post-SPIKE and schedule time with CMS team.
  • Workflow / permissions changes are NOT an MVP blocker. Very nice to have, our future selves will thank us.