search

department-of-veterans-affairs / va.gov-team

Public resources for building on and in support of VA.gov. Visit complete Knowledge Hub:
https://depo-platform-documentation.scrollhelp.site/index.html
283 stars 204 forks source link

Collaboration Cycle for Benefits Disability Experience Team, Disability Comp Application (21-526EZ), 526 Intro Pages #57349

Open alatempa24 opened 1 year ago

alatempa24 commented 1 year ago

VFS product information

VFS team name

Benefits Disability Experience Team

Product name

Disability Comp Application (21-526 EZ)

Feature name

526 Intro Pages

GitHub label for product

disability-experience

GitHub label for feature

No response

Kickoff questions

Toggle kickoff questions ### When did/will you start working on this product/feature? 4/12/23 ### 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 product/feature have Google Analytics tracking and a KPI dashboard in Domo? Yes ### Do you need to capture any additional analytics or metrics? Unsure ### Product outline https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/disability/526ez/README.md ### 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 ### Notify the Collaboration Cycle team of this ticket in the vfs-platform-support Slack channel. - [X] 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](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** See Platform guidance on [Design Intent artifacts](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/design-intent#Designintent-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. **This work is to redesign the introductory pages and flow at the start of 526. We will be rewriting and redesigning the introduction and start pages, and testing the pages and the new flow with veterans. Would love to hear at design intent feedback on whether we should create accessible prototypes for this research.** - [x] Whiteboard sketch or other [lo-fi wireframes](https://sketch.com/s/0fa92d93-0841-4c62-8112-c9c528204092) - [x] [User flow](https://sketch.com/s/0fa92d93-0841-4c62-8112-c9c528204092) - [ ] Research plan - [ ] Any other artifacts you have so far ##### Platform actions - [x] Design Intent Slack thread with VFS team: [Link](https://dsva.slack.com/archives/CBU0KDSB1/p1682438851282579) - [x] Meeting date/time: **Friday, April 28 at 11:30am 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 - [x] Accessibility has completed the review - [x] Design has completed the review - [x] IA has completed the review - [x] Update this ticket with the Zoom recording - Recording URL: [Link](https://drive.google.com/drive/u/1/folders/1R4XnJGXNSwhAKlRHV5vyHZpWgqHx6sWh) - Password: _no password needed_ ##### 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](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Sitewide-Content-and-IA-intake-request.2124906551.html) - [ ] Link to the Sitewide Content and IA Intake Request ticket below

Research Review

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

Toggle Midpoint Review #### Before meeting ##### VFS actions Navigate to reference link: [Midpoint Review Guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/midpoint-review) - [ ] 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" - [ ] 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) - [ ] 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. Provide links or documents for the following: **Please note content SOT and design prototypes are being updated based on feedback received from content on May 9.** - [x] Finalized design prototype or mockup: See prototypes page https://sketch.com/s/0fa92d93-0841-4c62-8112-c9c528204092 - [ ] Specify which pages are included in the review - [ ] Research plan - [ ] Conversation guide **Content artifacts** - [x] Your product’s content source of truth: https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/disability/526ez/design/introduction%20page%20content.md - [ ] Github ticket for any relevant static content page and entry point updates for tool or feature (if applicable) **IA artifacts** - [x] Please include a link to any [Sitewide Content & IA](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/sitewide-content-and-ia-intake-request) feedback you received, including an IA review document or intake form: https://github.com/department-of-veterans-affairs/va.gov-team/issues/57843 **QA artifacts** An artifact that corresponds to each standard in the [QA Standards](https://depo-platform-documentation.scrollhelp.site/developer-docs/quality-assurance-standards). - [ ] [Regression test plan](https://depo-platform-documentation.scrollhelp.site/developer-docs/quality-assurance-standards#QAstandards-regression-test-planRegressionTestPlan) - [ ] [Test plan](https://depo-platform-documentation.scrollhelp.site/developer-docs/quality-assurance-standards#QAstandards-test-planTestPlan) - [ ] [Coverage for References](https://depo-platform-documentation.scrollhelp.site/developer-docs/quality-assurance-standards#QAstandards-traceability-reportsTraceabilityReports) - [ ] [Summary(Defects) reports](https://depo-platform-documentation.scrollhelp.site/developer-docs/quality-assurance-standards#QAstandards-traceability-reportsTraceabilityReports) - [ ] [E2E tests](https://depo-platform-documentation.scrollhelp.site/developer-docs/quality-assurance-standards#QAstandards-e2e-test-participationE2ETestParticipation) (provide a link to the product’s code) - [ ] [Code coverage](https://depo-platform-documentation.scrollhelp.site/developer-docs/quality-assurance-standards#QAstandards-unit-test-coverageUnitTestCoverage) (provide a link to the product’s code) ##### Platform actions - [x] Midpoint review Slack thread with VFS team: - [x] Meeting date/time: May 12th at 2pm EST - [x] [Slack request](https://dsva.slack.com/archives/CBU0KDSB1/p1682438851282579) #### 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 - [x] Design has completed the review - [x] Accessibility has completed the review - [x] IA has completed the review - [ ] Content has completed the review - [ ] QA has completed the review - [x] Update this ticket with the Zoom recording - [Recording URL](https://oddball-io.zoom.us/rec/share/H4Mw6is050H2Uy2N8XkZTgGtpyLB0onH-R6abSUJ22-1FQReH6HcjnscamBZR5MI.ciwvV_vEAHMzknVZ) - Password: 5tuEXW&F ##### 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](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Analytics-request.1782120453.html) - [ ] 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](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Contact-center-review.1782317061.html) - [ ] 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](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/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](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) - [ ] **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 - [ ] Update this ticket with the Zoom recording - Recording URL: - 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 complete

Privacy, Security, Infrastructure Readiness Review

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
alatempa24 commented 1 year ago

Design intent scheduled 4/28/23 11:30am ET

RakshindaAslam commented 1 year ago

cc @RakshindaAslam

RakshindaAslam commented 1 year ago

@shiragoodman - Looking at the PSIRR page, it says that PSIRR reviews are not required for static pages (or iterations/updates to static pages). The intro pages changes are static in nature. Can you confirm that the PSIRR review is need here?

shiragoodman commented 1 year ago

@RakshindaAslam I just went and watched some of the Midpoint Review and Lydia's presentation of the changes. Since there are form fields, I would not classify this as static, and a PSIRR would be needed.

RakshindaAslam commented 1 year ago

@shiragoodman - the only form fields I noticed in @lydiahooper's presentation were to enter dates to progress to the page that was being changed, not adding new form fields to any page. But if that indicates, a PSIRR, we will plan for it. Please let us know.

shiragoodman commented 1 year ago

@RakshindaAslam PSIRR is one of those reviews where it's better safe than sorry. I would encourage you to submit a ticket an notify the Platform Security team as soon as possible. They will know for sure whether any review is needed.