Collaboration Cycle for [Conditions Team, 526ez, Multi-step conditions submission]

[yurenanava]

Please view the Milestone for all feedback and findings tickets associated with this Collaboration Cycle initiative.

VFS product information

VFS team name

Conditions Team

Product name

526ez Disability Benefits Application

Feature name

Multi-step conditions submission

GitHub label for team

contention-classification

GitHub label for product

21-526ez

GitHub label for feature

No response

Public DSVA Slack channel for VFS team

benefits-contention-classification

Kickoff questions

Toggle kickoff questions

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

October 2024

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...

Both

Does your work require non-trivial code changes or involve PII/PHI?

Unsure

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?

Unsure

Will a VA editor (Drupal) notice this change?

Unsure

Product outline

Initiative Brief

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

Add the GitHub labels for your team, product, and feature to this ticket.

• I acknowledge that I must add the GitHub labels for my team, product, and feature to this ticket.

Kickoff Slack Thread with VFS team: Kickoff thread

Collaboration Cycle touchpoints

PO Sync

Toggle PO Sync instructions

Note: The PO Sync touchpoint is for OCTO teams only. Non-OCTO teams are welcome to participate if they choose.

Before the meeting

OCTO Product Owner

• Review PO Sync Guidance to understand what this sync involves.
• Schedule your PO Sync (with at least 2 business days lead time from now):
  • Open the Calendly PO Sync calendar
  • Select a date and time and click "Confirm"
  • Add your name and email
  • Click "Schedule Event"
• Link all artifacts in the PO Sync artifacts for review section below at least two business days before the scheduled PO Sync. Please don't add artifacts in the comments section.

PO Sync artifacts for review
See guidance on PO Sync artifacts. Please provide links to artifacts at least two business days before the scheduled meeting.

Required:

• Product outline: Initiative Brief

Optional:

• Any other artifacts you have so far

Governance Team actions

• Meeting date/time: 11:00am - Tuesday, November 19, 2024 (Eastern Time - US & Canada)

After the meeting

OCTO Design Leads

• If the initiative receives OCTO alignment to proceed, add the PO-Sync-approved label to this ticket.
• If the initiative does not receive OCTO alignment to proceed, comment and close this ticket.

Design Intent

Toggle Design Intent instructions

Before the meeting

VFS team actions

• Review Design Intent Guidance to understand what this touchpoint involves.
• Schedule your Design Intent (with at least 2 business days lead time from now):
  • 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 email addresses for VFS team attendees
  • Click "Schedule Event"
• Link all artifacts in the Design Intent artifacts for review section below at least two business days before the scheduled Design Intent. Please don't add artifacts in the comments section.

Design Intent artifacts for review

See guidance on Design Intent artifacts. Governance Team feedback is based on the artifacts provided here as well as information provided during the meeting. Please provide links to artifacts at least two business days before the scheduled meeting.

Required:

• User flow

Not required, but nice to have:

• Wireframes (if provided, must include mobile wireframes)

Optional:

• Research plan
• Any other artifacts you have so far

Governance Team actions

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

After the meeting

Governance Team actions

• Update this ticket with the Zoom recording
  • Recording link
  • Passcode:
• Accessibility
  • Feedback added to milestone
  • No feedback
• Design
  • Feedback added to milestone
  • No feedback
• IA
  • Feedback added to milestone
  • No feedback

VFS team actions

• Review feedback tickets. Comment on the ticket if there are any questions or concerns.

Architecture Intent

Toggle Architecture Intent instructions

Before the meeting

VFS team actions

• Review Architecture Intent Guidance to understand what this touchpoint involves.
• Schedule your Architecture Intent (with at least 2 business days lead time from now):
  • Open the Calendly Architecture intent calendar
  • Select a date and time and click "Confirm"
  • Add your name and email
  • Click "Add Guests" and enter the email addresses for VFS team attendees
  • Click "Schedule Event"
• Link all artifacts in the Architecture Intent artifacts for review section below at least two business days before the scheduled Architecture Intent. Please don't add artifacts in the comments section.

Architecture Intent artifacts for review

See guidance on Architecture Intent artifacts. Feedback is based on the artifacts provided here as well as information provided during the meeting. Please provide links to artifacts at least two business days before the scheduled meeting.

Required:

• Fully completed Architecture Intent Meeting Template:
  • Conditions Team, 526ez - Multi-step conditions submission - 12-3-2024
• User data flow diagram, if your application accepts data from a user:
  • Va.gov Benefits forms - Normal backup emergency flows

Platform Team actions

• Meeting date/time: Dec 5, 2024 at 2:30pm ET

After the meeting

Platform Team actions

• Update this ticket with the Zoom recording
  • Recording link
  • Passcode:
• Engineering feedback
  • Feedback ticket attached to milestone
  • No feedback
• Mobile Engineering feedback
  • Feedback ticket attached to milestone
  • No feedback
• Security feedback
  • Feedback ticket attached to milestone
  • No feedback

VFS team actions

• Review feedback tickets. Comment on the ticket if there are any questions or concerns.

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)
• 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.

Required artifacts

• Design prototype or high-fidelity mockup (must include mobile prototype/mockup).
  • Specify which pages are included in the review: When testing the functional/s prototypes, consider using conditions from the list that mention a joint to test the follow-up questions where we ask for the side (left/right/bilateral), like "wrist sprain".
  • Figma link
  • Functional prototype: https://staging.va.gov/user-testing/new-conditions
• Up to date user flow
  • Guidance on user flows
  • Mural user flow link
• If working with Sitewide CAIA, link to CAIA intake ticket. CAIA Ticket

Not required, but nice to have artifacts

• Accessibility annotations included as part of your design. Included in Figma
• Research plan: link
• Links to specific CAIA artifacts:
  • IA spec
  • Content source of truth
• Any other artifacts you have so far

Platform actions

• Slack thread with VFS team
  
• Meeting date/time: 03:30pm - Tuesday, November 12, 2024 Rescheduled: 03:30pm - Tuesday, November 19, 2024 (Eastern Time - US & Canada)

After meeting

Platform actions

• Accessibility
  • Feedback added to milestone
  • No feedback
• Content
  • Feedback added to milestone
  • No feedback
• Design
  • Feedback added to milestone
  • No feedback
• IA
  • Feedback added to milestone
  • No feedback
• Update this ticket with the Zoom recording
  • Recording link
  • Passcode: ADw!6.dD

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"
• 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

Links to Staging Review artifacts must be added to this ticket 4 business days ahead of the scheduled meeting. Please do not make changes to the product or artifacts during the 4-day review period.

Required artifacts

• URL(s) to review the product
  • The product should be available on an approved staging environment.
  • List pages, sections of pages, and/or user flows impacted by this work.
• Drupal or Staging URL for updated primary entry point: the main way Veterans will access the tool through site navigation (not search)
  • If the primary entry point is not a page on VA.gov, include information about how to view it. Reach out to @platform-governance-team-members on Slack with any questions.
• Test users and scenarios (when applicable)
  • Store test user information, passwords, and tasks in a .md file in the va.gov-team-sensitive repository.
  • Make sure all user scenarios can be tested, i.e.: in-progress form, submitted form, new form.
• Link to Sitewide CAIA intake ticket, if applicable.
• Completed accessibility testing artifact: see instructions and link to accessibility testing template.
• QA Artifacts: artifacts that correspond to each of the QA Standards.
  • Regression test plan
  • Test plan
  • Coverage for References
  • Summary (Defects) reports
  • E2E tests
  • Code coverage
  • Endpoint monitoring playbook
  • Logging silent failures

Not required, but nice to have artifacts

• Content source of truth: link to CAIA Content feedback, such as a content source of truth.
• Information Architecture spec: link to CAIA IA feedback, such as an IA spec.

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
• Complete Collaboration Cycle feedback survey

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

[aprocik1]

Here's the related CAIA intake ticket that we'll be working on: 96484