FranECross
commented
3 weeks ago @shiragoodman Question about the order of touchpoints in the ticket. (I'm assuming they are in order of when we're supposed to complete them/schedule them?). For this ticket (and I would think for all tickets), is it possible to have the Research Review be just after Design Intent, which will place it before Architecture Intent. This is because our research sessions might introduce changes we want to make to the design, which would then impact the Architecture of the changes (or new app, if it was new). We won't have all the info for Architecture Intent until after the Research Sessions have completed and outcomes reviewed. TIA! cc @jilladams
shiragoodman
aprocik1
Please view the Milestone for all feedback and findings tickets associated with this Collaboration Cycle initiative.
VFS product information
VFS team name
Public Websites
Product name
Resources & Support
Feature name
Landing Page (including Search feature)
Design
Figma design
GitHub label for team
Public Websites
GitHub label for product
Resources and support
GitHub label for feature
R&S: Tagging/searching
Public DSVA Slack channel for VFS team
sitewide-public-websites
Kickoff questions
Toggle kickoff questions
### When did/will you start working on this product/feature? Research will be first, starting ~Nov 1st ### 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 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? Yes ### Product outline https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/resources-and-support/initiatives/2024-search-experience-enhancements-Phase-1 ### Verify all relevant materials provided to Governance Team - [x] 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. - [x] 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](https://dsva.slack.com/archives/C52CL1PKQ/p1729028020651709)Collaboration Cycle touchpoints
PO Sync 👉🏽 PASSED
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 - [x] Review [PO Sync Guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/po-sync) to understand what this sync involves. - [x] Schedule your PO Sync (with at least 2 business days lead time from now): _12:00pm - 12:30pm MT, Wednesday, October 30, 2024_ - Open the [Calendly PO Sync calendar](https://calendly.com/collaboration-cycle/po-sync) - Select a date and time and click "Confirm" - Add your name and email - Click "Schedule Event" - [x] 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.](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/po-sync#POSync-Whatartifactswillbeneeded?) Please provide links to artifacts **at least two business days** before the scheduled meeting. Required: - [x] Product outline - [Initiative - Resources and Support search experience enhancements, Phase 1](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/resources-and-support/initiatives/2024-search-experience-enhancements-Phase-1) Optional: - [x] Any other artifacts you have so far - Draft Design in [Figma](https://www.figma.com/design/cg8VNnxFOxw7lb10FVHpi5/VA-Resources-support-template?node-id=332-15356&node-type=section&t=LKPoCStziUafiWFD-0) ##### Governance Team actions - [ ] Meeting date/time: 02:00pm - Wednesday, October 30, 2024 #### After the meeting ##### OCTO Design Leads - [x] 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 👉🏽 SKIPPED
Toggle Design Intent instructions
#### Before the meeting ##### VFS team actions - [ ] Review [Design Intent Guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/design-intent) 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](https://calendly.com/collaboration-cycle/design-intent-or-midpoint-review) - 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.](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/design-intent#Designintent-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 👉🏽 TBD
Toggle Architecture Intent instructions
#### Before the meeting ##### VFS team actions - [ ] Review [Architecture Intent Guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/architecture-intent) 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](https://calendly.com/collaboration-cycle/architecture-intent) - 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.](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/architecture-intent#ArchitectureIntent-Whatartifactswillbeneeded?) 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](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/engineering/collab-cycle/architecture-intent-meeting.md) - [ ] [User data flow diagram](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/platform/practices/zero-silent-failures/how-to-create-a-user-data-flow-diagram.md), if your application accepts data from a user. ##### Platform Team actions - [ ] Meeting date/time: #### 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. - [ ]CMS Request 👉🏽 N/A
Toggle CMS Request
#### VFS actions - [ ] Complete the [CMS request process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/cms-request)Research Review 👉🏽 TBD
Toggle Research Review
#### VFS actions - [ ] Complete the [research review process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Research-plan-review.1781891143.html)Midpoint Review 👉🏽 Conducted 11/26/2024
Toggle Midpoint Review
#### Before meeting ##### VFS actions Navigate to reference link: [Midpoint Review Guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/midpoint-review) - [x] Schedule your Midpoint Review when ready: - Open the [Calendly midpoint review calendar](https://calendly.com/collaboration-cycle/design-intent-or-midpoint-review) - 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"  - [x] Check this box if you'd like this review to be asynchronous (Please refer to the [Midpoint Review guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Midpoint-review.1781039167.html) for the difference between a synchronous meeting and an asynchronous review) - [x] 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](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/midpoint-review#Midpointreview-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** - [x] [Design prototype or high-fidelity mockup](https://www.figma.com/design/cg8VNnxFOxw7lb10FVHpi5/Resources-support?node-id=332-15356&node-type=section&t=ymX1Z3sxtOcoT93R-0) (must include mobile prototype/mockup) - Specify which pages are included in the review - Main R&S page, with the filter component - The filter drawer that opens on the right - The tags that then display on search results that can be clicked (x) off or all cleared - [?] Up to date user flow - [Guidance on user flows](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/information-architecture/standards/user-flow-guidance.md) - Question: Can the [prototype ](https://www.figma.com/design/cg8VNnxFOxw7lb10FVHpi5/Resources-support?node-id=332-15356&node-type=section&t=ymX1Z3sxtOcoT93R-0)be used as a user flow? It covers the limited user flows available in Resources & Support. - [ ] If working with [Sitewide CAIA](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/sitewide-content-and-ia-intake-request), link to CAIA intake ticket. **Not required, but nice to have artifacts** - [ ] Accessibility annotations included as part of your design - [ ] Research plan - 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](https://dsva.slack.com/archives/C52CL1PKQ/p1731437105970919) - [ ] Meeting date/time: November 26, 2024 at 3.30 PM ET #### After meeting ##### Platform actions * Accessibility * [x] Feedback added to milestone * [ ] No feedback * Content * [ ] Feedback added to milestone * [ ] No feedback * Design * [x] Feedback added to milestone * [ ] No feedback * IA * [x] Feedback added to milestone * [ ] No feedback * [x] Update this ticket with the Zoom recording - [Recording link](https://oddball-io.zoom.us/rec/share/n-aJmTZc6VN446aeDlDS9rxSl-UO8MRhSzFSv18sNR0XPFy2PS5qERTtOxaEMM-f._G5_aqTIdTrzXByF) - Passcode: `+Mzb?^+9` ##### VFS actions - [ ] Review feedback tickets and comment on the ticket if there are any questions or concernsContact Center Review 👉🏽 TBD
Toggle Contact Center Review
#### VFS actions - [ ] Complete the [Contact Center review process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Contact-center-review.1782317061.html) - [ ] Link to the Contact Center review request ticket belowStaging Review 👉🏽 TBD
Toggle Staging Review
#### Before meeting ##### VFS actions - Navigate to reference link: [Staging Review Guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/staging-review) - [ ] Schedule your Staging Review when ready: - Open the [Calendly staging review calendar](https://calendly.com/collaboration-cycle/staging-review) - 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](https://design.va.gov/about/contributing-to-the-design-system/experimental-components-and-patterns), 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](https://depo-platform-documentation.scrollhelp.site/getting-started/vfs-product-directory). **Staging Review artifacts** Links to [Staging Review artifacts](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Staging-review.1810137181.html#Stagingreview-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](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/staging-environment-guidance-for-vfs-teams). - 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](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/Administrative/vagov-users/staging-test-accounts-accessible-example.md), 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](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/prepare-for-an-accessibility-staging-review). - [ ] **QA Artifacts:** artifacts that correspond to each of the [QA Standards](https://depo-platform-documentation.scrollhelp.site/developer-docs/quality-assurance-standards). - [ ] Regression test plan - [ ] Test plan - [ ] Coverage for References - [ ] Summary (Defects) reports - [ ] E2E tests - [ ] Code coverage - [ ] Endpoint monitoring playbook **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](https://depo-platform-documentation.scrollhelp.site/developer-docs/request-support-from-the-va-508-office#RequestsupportfromtheVA508office-AuditRequest). 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 completePrivacy, Security, Infrastructure Readiness Review 👉🏽 TBD
Toggle Privacy, Security, Infrastructure Readiness Review
#### VFS actions - [ ] Complete the [Privacy, security, infrastructure readiness review process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Privacy-and-security-review.1782317101.html) - [ ] Link to the Readiness Review ticket below #### Platform actions - [ ] Privacy, security, infrastructure readiness review is complete