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
277 stars 194 forks source link

Collaboration Cycle for the Public Websites Team for the Discharge Upgrade Wizard #80777

Open FranECross opened 2 months ago

FranECross commented 2 months ago

VFS product information

VFS team name

Public Websites

Product name

Discharge Upgrade Wizard

Feature name

The entire Discharge Upgrade Wizard, not a particular feature within it.

GitHub label for team

Public Websites

GitHub label for product

Discharge wizard

GitHub label for feature

N/A

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? Jan 25, 2024 ### 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... 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? Yes ### Product outline - https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/veteran-military-records/discharge-upgrade-wizard/initiatives/2024-discharge-upgrade-wizard-subtask/initiative-brief.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 - [Legacy User Flow in Mural with Legacy screenshots](https://app.mural.co/t/departmentofveteransaffairs9999/m/departmentofveteransaffairs9999/1696352911500/80253b1c7200212cbcbcfb940d2cf4a29fed8417?sender=u71e5a9ded413bfa79dd23932) ### 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. ### Notify the Collaboration Cycle team of this ticket in your team's public Slack channel. - [X] I acknowledge that I must notify the Governance team by completing the Collab Cycle Kickoff workflow in my team's Slack channel after submitting this issue. This can be completed by typing "/collab cycle" and selecting the kickoff workflow. Kickoff Slack Thread with VFS team: [Kickoff thread](https://dsva.slack.com/archives/C52CL1PKQ/p1713217994167679)

Recommended Collaboration Cycle touchpoints

Design Intent N/A

Before the meeting

VFS team actions

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:

Not required, but nice to have:

Optional:

Governance Team actions

After the meeting

Governance Team actions
VFS team actions

Research Review N/A

VFS actions

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) - [ ] Notify the Collaboration Cycle team of this event by using the `/Collab Cycle Midpoint Review` "slash-command" in your team channel. Provide information as prompted by the Slack workflow. - [ ] 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: - [ ] Finalized design prototype or mockup - [ ] Specify which pages are included in the review - [ ] Research plan - [ ] Conversation guide **Content artifacts** - [ ] Please include a link to any [Sitewide CAIA](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/sitewide-content-and-ia-intake-request) feedback you received, including a content source of truth, any relevant static content page and entry point updates, and the intake form. **IA artifacts** - [ ] Please include a link to any [Sitewide CAIA](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/sitewide-caia-intake-request) feedback you received, including an IA review document or intake form. ##### Platform actions - [ ] Slack thread with VFS team - [ ] Meeting date/time: #### After meeting ##### Platform actions * Accessibility * [ ] Feedback ticket attached * [ ] No feedback * Content * [ ] Feedback ticket attached * [ ] No feedback * Design * [ ] Feedback ticket attached * [ ] No feedback * IA * [ ] Feedback ticket attached * [ ] No feedback * [ ] Update this ticket with the Zoom recording - Recording link - Passcode: ##### 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" - [ ] Notify the Collaboration Cycle team of this event by using the `/Collab Cycle Staging Review` "slash-command" in your team channel. Provide information as prompted by the Slack workflow. - [ ] 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** See Platform guidance on [Staging Review artifacts](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Staging-review.1810137181.html#Stagingreview-Artifacts). Platform findings are based solely on the staging URL and test users provided, as reviewed during the four days before the Staging Review meeting. Any test cases not covered or any ongoing work taking place during the review period may not be reflected in those findings. **Product artifacts** - [ ] Staging URL - [ ] Specify which pages are included in the review - [ ] 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](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/Administrative/vagov-users/staging-test-accounts-accessible-example.md) in a .md file in the va.gov-team-sensitive repository. **Content artifacts** - [ ] Please include a link to any [Sitewide CAIA](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/sitewide-content-and-ia-intake-request) feedback you received, including a content source of truth, any relevant static content page and entry point updates, and the intake form. **IA artifacts** - [ ] Please include a link to any [Sitewide CAIA](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/sitewide-caia-intake-request) feedback you received, including an IA review document or intake form. **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 - [ ] Test plan - [ ] Coverage for References - [ ] Summary(Defects) reports - [ ] E2E tests - [ ] Code coverage **Accessibility artifacts** - [ ] [Completed accessibility testing artifact](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=briandeconinck&labels=a11y-testing&template=a11y-testing.yaml&title=Accessibility+Testing+for+%5BTeam+Name%2C+Product+Name%2C+Feature+Name%5D). For details, see [Prepare for an accessibility staging review](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/prepare-for-an-accessibility-staging-review). ##### 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 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
jilladams commented 2 months ago

@FranECross @aklausmeier (cc @thejordanwood) Discharge Upgrade Wizard collab cycle ticket here is recommending some touchpoints we need to figure out / maybe talk to Governance folks about:

  1. Design Intent: We're using the DS subtask pattern the same way we did for Income Limits and PACT Act wizards, and we don't have a design artifact other than our user flow for that reason. So: we likely need to talk to Governance folks about what's required here from their perspective.
  2. Research review: Same. We aren't currently planning to run research, because we're moving from a deprecated pattern to a DS pattern.
  3. Midpoint: Same. We won't have any additional artifacts for this touchpoint. I think we might be able to propose skipping Design Intent and Research Review, and jump right to requesting an async Midpoint.

Thoughts?

FranECross commented 2 months ago

@coforma-terry I'm not sure how or who to approach regarding Jill's points above. Would I just note things in the ticket in the appropriate sections as to why we believe that particular review wouldn't be relevant/the info we have would be sufficient, and then do the async when I request a midpoint review? Thanks in advance for your guidance!

jilladams commented 2 months ago

@shiragoodman ^^ These might also be questions for you.

shiragoodman commented 2 months ago

@FranECross @jilladams Both the Design Intent and Midpoint Review are optional touchpoints, so if you'd like to skip them for any reason, you're welcome to. The Research Review is only required if you're planning to do research with Veterans or if you're doing any experimental design. We won't allow proposed component changes/uses to be published to VA.gov unless the solution has been tested. LMK if you have any other questions.