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

Prep for VBA Midpoint review #10473

Closed
17 tasks done
davidmpickett opened this issue Aug 25, 2022 · 17 comments
Closed
17 tasks done

Prep for VBA Midpoint review #10473

davidmpickett opened this issue Aug 25, 2022 · 17 comments
Assignees
Labels
Facilities Facilities products (VAMC, Vet Center, etc) Product management Regional office CMS managed VBA product owned by the Facilities team sitewide Sprint goal

Comments

@davidmpickett
Copy link
Contributor

davidmpickett commented Aug 25, 2022

Description

Acceptance Criteria

  • Main artifacts to create: product design vision & decision overview
    • Contextualize VBA as iteration/extension of VAMC and Vet Centers
      • Emphasize editor-driven content
    • Clarify what we are trying to do and what & we want feedback on
      • Collapsed accordions
        • Top Tasks
        • Hours -> two sets of hours per day & time zone support
        • Escape hatch for "can't find the service?"
      • Expanded accordions
        • Services -> combining Appointment info into Service Location
        • Services -> improving semantic and visual separation for multiple Service Locations
        • Services -> Adding modality / service delivery type (virtual/in-person/online-self service)
  • Artifacts for midpoint review have been agreed upon and approved by Facitilites Team / PO
  • Midpoint review section of collab cycle ticket is complete
  • Midpoint review is requested - @jilladams to help
@davidmpickett davidmpickett added Design CMS team practice area Needs refining Issue status Regional office CMS managed VBA product owned by the Facilities team labels Aug 25, 2022
@davidmpickett davidmpickett added the Facilities Facilities products (VAMC, Vet Center, etc) label Aug 25, 2022
@davidmpickett
Copy link
Contributor Author

The collaboration cycle flow diagram implies that Design Intent should precede Research Reviews. But it also says that we should have a lo-fi prototype, so maybe this is more like "Research Intent" to talk about all the research we're planning to do?

Just want to make sure we're clearing the path for #10193

@davidmpickett
Copy link
Contributor Author

Looking back at Vet Centers as a model, it seems like they did a round of research before creating a lo-fi wireframe and scheduling Design Intent, so it doesn't seem like this is actually a blocker. Going to take this off this sprint.

@dsinla dsinla removed their assignment Aug 29, 2022
@dsinla
Copy link
Contributor

dsinla commented Aug 31, 2022

I think @RWEagans and I popped this back on the sprint yesterday when we reviewed all the issues, thinking it was accidentally left off. It seems as @davidmpickett has said, this first collab cycle touchpoint will expect a lo-fi wireframe, and that will come after initial research, which is still a few sprints out.

Removing from sprint 66....again....

@davidmpickett davidmpickett removed their assignment Feb 23, 2023
@davidmpickett davidmpickett changed the title PM/DSN: Prep for VBA Design Intent PM/DSN: Prep for VBA Midpoint review May 24, 2023
@davidmpickett davidmpickett changed the title PM/DSN: Prep for VBA Midpoint review Prep for VBA Midpoint review May 24, 2023
@davidmpickett
Copy link
Contributor Author

@kmariepat-cityfriends @mmiddaugh - flagging this for refinement tomorrow. This used to be a "prep for design intent" card, but likely to be more of a "prep for midpoint review" card now

@davidmpickett
Copy link
Contributor Author

davidmpickett commented May 25, 2023

@kmariepat-cityfriends @mmiddaugh @jilladams

In talking with @thejordanwood and @cindymerrill today we came up with a mini timeline for VBA Design and Usability Testing. Wanted to confirm this aligns with your expectations

  • Get design close to final by end of this current sprint (Jun 6th)
  • Have Midpoint Review early next sprint (Jun 8th?)
  • Jordan could turn the VBA design into a clickable prototype by the end of next sprint (Jun 20th)
  • As prototype is being finalized Cindy/Alexis would begin finalizing Research Plan + Conversation guide and map out timeline for recruitment and research sessions
  • Usability sessions take place in early/mid July?

@cindymerrill
Copy link
Contributor

Thanks for writing this up, @davidmpickett ! A few more updates to add:

  • While I'm waiting for the design to get populated with content, I'm going to review the new content from Dave and start drafting some potential user tasks for the conversation guide. (current sprint)
  • @thejordanwood thought it wouldn't take long to put together a prototype for this single page (much less than a sprint), and we should talk about what screens we think we'll need (current sprint?)
  • I'll start thinking about a timeline for the research, which will only be a draft until we know the results of the Midpoint Review and what screens we need for the prototype. Hoping for June, not July, but we'll see how the design/content goes. (current - next sprint; dependency on the completion of the design and prototype)
  • My understanding is that I'll be the one finalizing the Research Plan and Conversation Guide, not Alexis (who will be shadowing me). (current - next sprint; dependency on the completion of the design and prototype)

FYI I'm planning 1.5 weeks of PTO for late June / early July (specific dates TBD), which will affect the research timeline.
@jilladams @mmiddaugh @kmariepat-cityfriends

@thejordanwood
Copy link

@cindymerrill Correct, it won't take me long to put together a prototype for this. The prototype is very dependent on when content gets finalized and when midpoint review happens. I think June 20th is a good estimate for now, and we can possibly have it finished sooner if things go smoothly.

@cindymerrill
Copy link
Contributor

@davidmpickett @thejordanwood IF the content gets finalized and the Midpoint Review happens on June 8, I would think that we wouldn't need 1.5 weeks to make changes and build the prototype? I'm trying to fit in the research sessions before I leave on vacation, which is likely during the last week of June.

@davidmpickett
Copy link
Contributor Author

I want to note on this ticket that one of the major activities we undertook this sprint to prep for Midpoint review was to meet with the Sitewide Content team about ticket department-of-veterans-affairs/va.gov-team#58511

@jilladams
Copy link
Contributor

Lane was affected by the workflow integration with the Speedrun board. Moving back to Sprint backlog.

@kmariepat-cityfriends
Copy link

Per @davidmpickett's comment, met with the sitewide content team and are awaiting their feedback ahead of being unblocked for midpoint review

cc @jilladams

@jilladams jilladams added Product management and removed Design CMS team practice area labels Jul 6, 2023
@jilladams
Copy link
Contributor

From UX refinement: if content comes in & design is updated / we are otherwise ready for Midpoint review while I'm out, @mmiddaugh will help schedule the collab cycle touchpoint.

@jilladams
Copy link
Contributor

@davidmpickett
Copy link
Contributor Author

davidmpickett commented Jul 24, 2023

Shared collapsed accordion artifacts with team for review: https://dsva.slack.com/archives/C0FQSS30V/p1690238772318379

@davidmpickett
Copy link
Contributor Author

@davidmpickett
Copy link
Contributor Author

Artifacts were approved in #14087 today. Also @thejordanwood fixed my typos and reorganized the Open service accordion page and it's beautiful

@davidmpickett
Copy link
Contributor Author

And I messaged platform to let them know the artifacts are ready. DONEZO

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) Product management Regional office CMS managed VBA product owned by the Facilities team sitewide Sprint goal
Projects
None yet
Development

No branches or pull requests

6 participants