Collaboration Cycle for Digitize Forms - Form 21-4142(a)

[tbaker1026]

VFS product information

VFS team name

Digitize Forms

Product name

Form 21-4142(a)

Feature name

Form 21-4142(a)

GitHub label for product

21-4142

GitHub label for feature

No response

Kickoff questions

Toggle kickoff questions

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

2/20/2023

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

Yes

Are you doing research with VA.gov users?

No

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-forms/blob/main/Forms/21-4142(a)/Product%20Outline.md

Notify the Collaboration Cycle team of this ticket in the vfs-platform-support Slack channel.

• I acknowledge that I must notify #vfs-platform-support after submitting this issue.

Recommended Collaboration Cycle touchpoints

Design Intent

Toggle Design Intent

Before meeting

VFS 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

• Sketches and User Flow
• Source of Truth

Platform actions

• Follow Moderator Responsibilities guidance for Design Intent
• Meeting date/time: Monday, March 6 3:30PM ET

After meeting

Platform actions

• If you have feedback, create feedback tickets and link to this epic. Once you have completed you review, check the box next to your practice area
  • Accessibility has completed the review
  • Design has completed the review
  • IA has completed the review
• Update this ticket with the Zoom recording
  • Recording URL: https://oddball-io.zoom.us/rec/share/lwOqmI_GI_5hQ3cY-aKEOKORhHII8swDoK5wzHS-FrT3IjY_UJ_mEcBO_7aHgQOs.IXtRP6d8LBo3RH1U
  • Password: mCHE3O2#

VFS actions

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

Sitewide Content and IA Intake Request

Toggle Sitewide Content and IA Intake Request

VFS actions

• Complete the sitewide content and IA intake request process
• Link to the Sitewide Content and IA Intake Request ticket below - epic [Epic] Form 21-4142(a) #55195

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

Provide links or documents for the following:

• Finalized design prototype or mockup
• Specify which pages are included in the review
• Research plan
• Conversation guide

Content artifacts

• Source of Truth
• Github ticket for any relevant static content page and entry point updates for tool or feature (if applicable)

IA artifacts

• Please include a link to any Sitewide Content & IA 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)

Platform actions

• Follow Moderator Responsibilities guidance for Midpoint Review
• Meeting date/time: Thursday, April 6 at 1:30 pm EST
• Slack request

After meeting

Platform actions

• If you have midpoint review feedback, create feedback ticket and link to this epic. Once you have completed your review, check the box next to your practice area
  • Design has completed the review
  • Accessibility has completed the review
  • IA has completed the review
  • Content has completed the review
• Update this ticket with the Zoom recording
  • Recording URL: Zoom link
  • Password: $Z%sXk0%

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

Platform guidance on Staging Review artifacts

Product artifacts
PLEASE SEE GITHUB PAGE FOR ALL SUPPORTING ARTIFACT LISTED BELOW

• Staging URL
• All Pages, new Form
• 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

• Github ticket for any relevant static content page and entry point updates for tool or feature (if applicable)

IA artifacts

• Please include a link to any Sitewide Content & IA 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 Link to Test Rails
• Coverage for References Coverage Link
• Summary(Defects) reports
• E2E testsprovide 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

• Follow Moderator Responsibilities guidance for Staging Review
• Meeting date/time: Thursday, June 15, 2023 at 2:00PM Eastern
• Slack thread with the VFS team: #vfs-platform-support Slack thread

After meeting

Platform actions

• Update this ticket with the Zoom recording
  • Recording URL: Link
  • Password: crn2CyU=

VFS actions

• Review feedback tickets and comment on the ticket if there are any questions or concerns
• Close individual feedback 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