Usability Testing Prep - eBenefits ["Your VA payments"]

[jason-gcio]

Steps to complete Usability Testing Prep:

• [x] Product Manager: create this issue and fill in the team name and feature name in the title and other bolded information appropriately
• [x] Attach all artifacts before requesting the meeting
• [x] Link to this issue once created in #vfs-platform-support in Slack; tag @ Shira Goodman and @ Andrea Hewitt
• [x] Shira to schedule meeting with VSP reviewers and eBenefits attendees (as listed below)
• [x] At least 2 days before scheduled meeting, you must complete list of artifacts below
• [x] Usability Testing Prep review meeting completed
• [x] Practice area reviewers create sub-issues attached to this one with feedback for your team on "View my VA payment history"
• [ ] Requesting team completes attached feedback tickets based on definition of done included in each practice area feedback ticket (may differ for each practice area, please refer to attached tickets for further instruction)

Artifacts - please provide the following artifacts at least 2 days before scheduled meeting

• Link to product outline
• Link to prototype
• Link to or attach artifact with copy (if separate from prototypes/mockups)
• Link to research plan and script
• Link to regression test plan for QA practice area review
• Link to test cases/test plan in TestRail for QA practice area review

Meeting attendees from eBenefits

• Product Manager (required): Jason Wolf
• DEPO product lead (required): Steve Kovacs
• Designer/Researcher: Jim Adams

Scheduling

• Please reference the VSP Collaboration Meetings Calendar (times shown are ET)
• Note an available time slot within a recurring "[CALENDAR BLOCK] Review Group Office Hours" slot that works for your team and is at least 2 business days from now
• Write that preferred time slot here (on this ticket), and VSP will send you a meeting invite: Friday, October 30, 2-2:30 pm ET
• If no available time slots work for your team, write your availability and requirements here and Shira will reach out as needed

Additional Notes:

During this collaboration point, you will receive feedback from the following practice areas: design, accessibility, content, QA, and optional: information architecture (IA), product

[shiragoodman]

@jason-gcio for future reference, you don't need to put your teams emails in the meeting attendees section. Although I greatly appreciate it, there could be pii/phi concerns. Names should suffice and I will pull emails from Slack.

[tlei123]

FYI, @jason-gcio , I've started a Test Plan ticket #15648 to track test planning. User-scenarios list there have been fleshed out to reflect additional cases as suggested by @pjhill , with links to TestRail test-cases links added.