Closed loripusey closed 2 years ago
@loripusey I'm going to see if I can grab time with you tomorrow to review this - https://docs.google.com/presentation/d/1Y8JFwpkY85blzt1IvKx-35AZ9FaaYBdoGrFONK-vPfs/edit?usp=sharing
I just have a couple set-up slides that i still need to add. But, feel free to review if you'd like.
@kristenmcconnell FYI, I made the updates that we discussed
Finished these
Just need to post to research repo and message lori about change I made to recos, e.g., pre-check-in name change.
@loripusey the only ticket that I think you may not have from the recommendations is this one that I updated:
Explore new naming convention for “pre-check-in” that doesn’t include “check-in.” Specifically, draft new ideas and document usage across Veteran and staff-facing applications. Consider how pre-check-in may be perceived by Veterans once new functionality is introduced and considered more valuable compared to current state. E.g., health questionnaires, editing information and medication review.
Link to Bay Pines presentation to look at recommendations
To recap, I think our team's tickets would be (not including VSE, VSE-CS tickets):
Co-work with VeText/CHIP:
Vet-facing team
Long term:
User Story
Related Documentation
Description
A research report detailing findings and design recommendations from the June 22 study.
Reference Materials
Tasks
Acceptance Criteria