-
Notifications
You must be signed in to change notification settings - Fork 70
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
Comments
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 |
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. |
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.... |
@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 |
@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
|
Thanks for writing this up, @davidmpickett ! A few more updates to add:
FYI I'm planning 1.5 weeks of PTO for late June / early July (specific dates TBD), which will affect the research timeline. |
@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. |
@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. |
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 |
Lane was affected by the workflow integration with the Speedrun board. Moving back to Sprint backlog. |
Per @davidmpickett's comment, met with the sitewide content team and are awaiting their feedback ahead of being unblocked for midpoint review cc @jilladams |
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. |
|
Shared collapsed accordion artifacts with team for review: https://dsva.slack.com/archives/C0FQSS30V/p1690238772318379 |
My magnum opus is complete https://www.sketch.com/s/891d33ae-152d-471c-ab5d-9aedf89cf6ff/p/578C3207-C5A3-4303-AB18-4AFC27AC54D2/canvas |
Artifacts were approved in #14087 today. Also @thejordanwood fixed my typos and reorganized the Open service accordion page and it's beautiful |
And I messaged platform to let them know the artifacts are ready. DONEZO |
Description
Acceptance Criteria
The text was updated successfully, but these errors were encountered: