Collaboration Cycle for Identity, Login, Guardian Access

[joellewells]

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

VFS product information

VFS team name

Identity

Product name

Login

Feature name

Guardian Access

GitHub label for team

identity

GitHub label for product

identity-ux

GitHub label for feature

No response

Public DSVA Slack channel for VFS team

#secure-sign-in-transition

Kickoff questions

Toggle kickoff questions

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

10/1/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...

Static pages

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

No

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?

No

Will a VA editor (Drupal) notice this change?

No

Product outline

https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity/Products/Product%20Briefs/PRD%20-%20Court-Appointed%20Guardian%20Access.md

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

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 with mobile viewport

Optional:

• Research plan
• Any other artifacts you have so far

Governance Team actions

• Design Intent Slack thread with VFS team
• Meeting date/time: Friday, November 22, 2024 at 2:00pm ET

After the meeting

Governance Team actions

• Update this ticket with the Zoom recording
  • Recording link
  • Passcode: ^1X!jUhY
• Accessibility
  • Feedback ticket included in milestone
  • No feedback
• Design
  • Feedback ticket included in milestone
  • No feedback
• IA
  • Feedback ticket included in milestone
  • No feedback

VFS team actions

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

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

[joellewells]

@claytonzook

[joellewells]

@it-harrison Just double checking. Do we need a PO sync here? I've never done one before but wanted to make sure!