Collaboration Cycle for Benefits team 1, Claim status tool , Claim Phase Experience

[uxgary]

VFS product information

VFS team name

Benefits team 1

Product name

Claim status tool

Feature name

Claims process overview page

GitHub label for product

claim-status-tool

GitHub label for feature

n/a

Public DSVA Slack channel for VFS team

#benefits-management-tools

Kickoff questions

Toggle kickoff questions

When did/will you start working on this product/feature?

July 12, 2023

Will your work result in visible changes to the user experience?

Yes

Are you doing research with VA.gov users?

Yes

Will your work involve changes to...

Tools, applications and dynamic pages

Does your product/feature have Google Analytics tracking and a KPI dashboard in Domo?

Yes

Do you need to capture any additional analytics or metrics?

Yes

Product outline

https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/claim-appeal-status/CST%20Product/Product%20Outline.md

Initiative Brief

https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/claim-appeal-status/CST%20Product/Improved%20Claims%20Process%20Understanding%20Initiative.md

Screenshots

Before

Current designs posted in a mural board

After

Proposed design in a mural board

Verify all relevant materials provided to Governance Team

• I have provided all relevant and up-to-date links, screenshots, images, designs, etc. of the as-is version of the product

Notify the Collaboration Cycle team of this ticket in your team's public Slack channel.

• I acknowledge that I must notify the Governance team by completing the collab cycle kicckoff workflow in my team's Slack channel after submitting this issue. This can be completed by typing "/collab cycle" and selecting the appropriate workflow.

Kickoff Slack Thread with VFS team: Kickoff thread

Recommended Collaboration Cycle touchpoints

Design Intent

Toggle Design Intent

Before meeting

VFS actions

• Navigate to reference link: Design Intent Guidance
• Schedule your Design Intent when ready:
  • Open the Calendly design intent calendar
  • Select a date and time and click “Confirm”
  • Add your name and email
  • Click "Add Guests" and enter the VFS meeting attendees email addresses
    • Invite all relevant VFS team members, including accessibility support, product owners, and other VA stakeholders
    • The Governance team is responsible for inviting our team members, including our Product Owner, Product Manager, and practice area specialists. We also notify OCTO-DE practice area leads when we finalize meeting scheduling.
  • Click "Schedule Event"
• Notify the Collaboration Cycle team of this event by using the /Collab Cycle Design Intent "slash-command" in your team channel. Provide information as prompted by the Slack workflow.
• Link all artifacts ONLY in the Design Intent artifacts section below at least two days before the scheduled Design Intent. Do NOT add artifacts to Comments section

Design Intent artifacts

• Link to the mural board we will be presenting during design intent.
• Research plan [Github]

** Team Members who will be in attendance**

• Jacob Worrell (jacob.worrell@adhocteam.us)
• Skyler Schain (skyler@coforma.io)
• Lauren Sinreich (lauren.sinreich@coforma.io)
• Julie Strothman (julie.strothman@va.gov)

See Platform guidance on Design Intent artifacts. Platform feedback is based solely on the artifacts provided, as reviewed during the two days before the Design Intent meeting. Any work not included in the artifacts below or any ongoing work taking place during the review period may not be reflected in that feedback.

• User flow (required)
• Whiteboard sketch or other lo-fi prototypes or wireframes
• Research plan
• Any other artifacts you have so far

Platform actions

• Slack thread with VFS team
• Meeting date/time: Friday, December 15, 2023, at 11:30 a.m. Eastern

After meeting

Platform actions

• Accessibility
  • Feedback ticket attached
  • No feedback
• Design
  • Feedback ticket attached
  • No feedback
• IA
  • Feedback ticket attached
  • No feedback
• Update this ticket with the Zoom recording
  • Recording link: https://oddball-io.zoom.us/rec/share/4demsF8oQQ0zyRPTcp5R12BmB8bkFYVW07U9pYh-ySgSH7zme6smN0cegk6Q_mH6.Lk7UOkTlZkV_DtnX
  • Passcode: 8qs4@z^g

VFS actions

• Review feedback tickets and comment on the ticket if there are any questions or concerns

Sitewide CAIA Intake Request

Toggle Sitewide CAIA Intake Request

VFS actions

• Complete the Sitewide CAIA intake request process
• Link to the Sitewide CAIA Intake Request ticket below

Research Review

Toggle Research Review

VFS actions

• Complete the research review process

Midpoint Review

Toggle Midpoint Review

Before meeting

VFS actions

Navigate to reference link: Midpoint Review Guidance

• Schedule your Midpoint Review when ready:
  • Open the Calendly midpoint review calendar
  • Select a date and time and click “Confirm”
  • Add your name and email
  • Click "Add Guests" and enter the VFS meeting attendees email addresses
    • Invite all relevant VFS team members, including accessibility support, product owners, and other VA stakeholders
  • Click "Schedule Event"
• Check this box if you'd like this review to be asynchronous (Please refer to the Midpoint Review guidance for the difference between a synchronous meeting and an asynchronous review)
• Notify the Collaboration Cycle team of this event by using the /Collab Cycle Midpoint Review "slash-command" in your team channel. Provide information as prompted by the Slack workflow.
• Link all artifacts ONLY in the Midpoint Review artifacts section below at least two days before the scheduled Midpoint Review. Do NOT add artifacts to Comments section

Midpoint Review artifacts

See Platform guidance on Midpoint Review artifacts. Platform feedback is based solely on the artifacts provided, as reviewed during the two days before the Midpoint Review meeting. Any work not included in the artifacts below or any ongoing work taking place during the review period may not be reflected in that feedback.

Provide links or documents for the following:

• Finalized design mocks included in Mural board
• The page title in the Fima file is called, Midpoint review
• Research plan
• Conversation guide

Content artifacts

• Content edits [Figma] **Note: ** A member of the CAIA team completed her content edits directly in the figma file. The page title in the Fima file is called, CAIA Edits

IA artifacts

• see "CAIA edits" above).

Platform actions

• Slack thread with VFS team
• Meeting date/time: Tuesday, April 30, 2024 at 3:30 p.m. Eastern

After meeting

Platform actions

• Accessibility
  • Feedback ticket attached
  • No feedback
• Content
  • Feedback ticket attached
  • No feedback
• Design
  • Feedback ticket attached
  • No feedback
• IA
  • Feedback ticket attached
  • No feedback
• Update this ticket with the Zoom recording
  • Recording link: https://oddball-io.zoom.us/rec/share/wdsnvka5IwWnbDme8Q-s2Dwf8YCy79fcZ9LhuiZ-Zy3VbQ2CFfuxfGvm3MRXyu51.kr3jv4NOQtU-ztGB
  • Passcode: D5cQ?5D#

VFS actions

• Review feedback tickets and comment on the ticket if there are any questions or concerns

Analytics Request

Toggle Analytics Request

VFS actions

• Complete the analytics request process
• Link to the Analytics Implementation and QA Request ticket below

Contact Center Review

Toggle Contact Center Review

VFS actions

• Complete the Contact Center review process
• Link to the Contact Center review request ticket below

Staging Review

Toggle Staging Review

Before meeting

VFS actions

• Navigate to reference link: Staging Review Guidance
• Schedule your Staging Review when ready:
  • Open the Calendly staging review calendar
  • Select a date and time and click “Confirm”
  • Add your name and email
  • Click "Add Guests" and enter the VFS meeting attendees email addresses
    • Invite all relevant VFS team members, including accessibility support, product owners, and other VA stakeholders
  • Click "Schedule Event"
• Notify the Collaboration Cycle team of this event by using the /Collab Cycle Staging Review "slash-command" in your team channel. Provide information as prompted by the Slack workflow.
• If this product contains any experimental design, add the experimental-design label and schedule a meeting with DSC to present the research findings.
• Link all artifacts ONLY in the Staging Review artifacts section below at least four days before the scheduled Staging Review. Do NOT add artifacts to Comments section
• I confirm the environment is available and test users have been provided.
• Please verify your product information in the Product Directory.

Staging Review artifacts

See Platform guidance on Staging Review artifacts. Platform findings are based solely on the staging URL and test users provided, as reviewed during the four days before the Staging Review meeting. Any test cases not covered or any ongoing work taking place during the review period may not be reflected in those findings.

Product artifacts

• Staging URL
• Specify which pages are included in the review
• Staging test user information

Note: Please double-check that you've provided staging access information appropriate for testing the tool or feature. Don't put staging credentials in your va.gov-team ticket; store test user information, passwords, and tasks in a .md file in the va.gov-team-sensitive repository.

Content artifacts

• Please include a link to any Sitewide CAIA feedback you received, including a content source of truth, any relevant static content page and entry point updates, and the intake form.

IA artifacts

• Please include a link to any Sitewide CAIA feedback you received, including an IA review document or intake form.

QA artifacts

An artifact that corresponds to each standard in the QA Standards.

• Regression test plan
• Test plan
• Coverage for References
• Summary(Defects) reports
• E2E tests (provide a link to the product’s code)
• Code coverage (provide a link to the product’s code)

Accessibility artifacts

• Completed accessibility testing artifact. For details, see Prepare for an accessibility staging review.

Platform actions

• Slack thread with VFS team
• Meeting date/time:

After meeting

Platform actions

• Update this ticket with the Zoom recording
  • Recording link
  • Password:

VFS actions

• Review the findings tickets and comment on the ticket if there are any questions or concerns
• Close individual findings tickets when the issue has been resolved or validated by your Product Owner. If a team has additional questions or needs Platform help validating the issue, please comment on the issue ticket.
• After launch, request an accessibility audit from the VA 508 Office. This is required even if no accessibility issues were found during the Staging Review.
  • Share ServiceNow ticket number here: ______
• Close ticket once Privacy, Security, Infrastructure Readiness Review has been completed, VA 508 Office audit is requested, and all other post-Staging actions are complete

Privacy, Security, Infrastructure Readiness Review

Toggle Privacy, Security, Infrastructure Readiness Review

VFS actions

• Complete the Privacy, security, infrastructure readiness review process
• Link to the Readiness Review ticket below

Platform actions

• Privacy, security, infrastructure readiness review is complete

[erinrwhite]

Hi folks, IA feedback for Design Intent added a bit late as I was unexpectedly OOO yesterday. Thank you!