Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Collaboration Cycle for [Disability Benefits Experience Team 1, Disability Comp Application (21-526 EZ), Submission Experience] #86117

Open
24 of 76 tasks
mengA6 opened this issue Jun 17, 2024 · 4 comments
Open
24 of 76 tasks

Collaboration Cycle for [Disability Benefits Experience Team 1, Disability Comp Application (21-526 EZ), Submission Experience] #86117

mengA6 opened this issue Jun 17, 2024 · 4 comments
Labels
cc-kickoff collaboration-cycle For VSP Collaboration Cycle requests and improvements DBEX-TREX Disability Benefits Experience - Team T-Rex disability-experience midpoint-review Collaboration Cycle Midpoint Review sitewide CAIA
Milestone
Collaboration Cyc...

Comments

@mengA6
Copy link
Contributor

mengA6 commented Jun 17, 2024 •
edited
Loading

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

VFS product information

VFS team name

Disability Benefits Experience Team 1

Product name

Disability Comp Application (21-526 EZ)

Feature name

Submission Experience

GitHub label for team

DBEX-TREX

GitHub label for product

disability-experience

GitHub label for feature

No response

Public DSVA Slack channel for VFS team

#benefits-disability

Kickoff questions

Toggle kickoff questions

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

March, 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...

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/product/feature-briefs/Submission%20Experience.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.

Notify the Collaboration Cycle team of this ticket in your team's public Slack channel.

  • 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

Recommended 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"
  • Notify the Collaboration Cycle team of this event by using the /Collab Cycle Design Intent slash-command in your team channel. Provide information as prompted by the Slack workflow.
  • 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:

Not required, but nice to have:

  • Wireframes - Figma (actually high fidelity design. we don't have wireframes.)

Optional:

  • Research plan
  • Any other artifacts you have so far
Governance Team actions
  • Originally scheduled as design intent, converted to midpoint review.

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.

Research Review

Toggle Research Review

VFS actions

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)
  • 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. 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 - Figma
  • Specify which pages are included in the review - Figma page "WIP 6/10/2024 - current state of other products"
  • Research plan
  • Conversation guide

Also see the initiative brief

Content artifacts

  • Please include a link to any Sitewide CAIA feedback you received, including a content source of truth, any relevant static content page and entry point updates, and the intake form.

We have this old CAIA intake request, but it's based on an old plan for the work where we were designing toward the future state of Claim Status Tool and My VA after the VFF team initiative. Some of it is not relevant anymore.

IA artifacts

  • Please include a link to any Sitewide CAIA feedback you received, including an IA review document or intake form.

See above

Platform actions

After meeting

Platform actions
  • Accessibility
    • Feedback added to milestone
    • No feedback
  • Content
    • Feedback added to milestone
    • No feedback
  • Design
    • Feedback added to milestone
    • No feedback
  • IA
    • Feedback added to milestone
    • No feedback
  • Update this ticket with the Zoom recording
VFS actions
  • Review feedback tickets and comment on the ticket if there are any questions or concerns

Analytics Request

Toggle Analytics Request

VFS actions

Contact Center Review

Toggle Contact Center Review

VFS actions

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"
  • 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, 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

See Platform guidance on Staging Review 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 in a .md file in the va.gov-team-sensitive repository.

Content artifacts

  • Please include a link to any Sitewide CAIA 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 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
  • Code coverage

Accessibility artifacts

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

Privacy, Security, Infrastructure Readiness Review

Toggle Privacy, Security, Infrastructure Readiness Review

VFS actions

Platform actions

  • Privacy, security, infrastructure readiness review is complete
@mengA6 mengA6 added collaboration-cycle For VSP Collaboration Cycle requests and improvements CC-Request Consolidated GitHub issue for Collaboration Cycle touchpoints sitewide CAIA disability-experience DBEX-TREX Disability Benefits Experience - Team T-Rex and removed CC-Request Consolidated GitHub issue for Collaboration Cycle touchpoints labels Jun 17, 2024
@mengA6 mengA6 mentioned this issue Jun 17, 2024
Open
@mengA6
Copy link
Contributor Author

mengA6 commented Jun 17, 2024 •
edited
Loading

Slack thread

The design ticket we are working on is Complete design for "Give Vet clear expectations of claim status"#84850.

Current working Figma page

@mengA6
Copy link
Contributor Author

mengA6 commented Jun 17, 2024

We are fairly far along in the design and currently crafting a research plan. One question I have is whether we can combine Design Intent & Midpoint Review since I believe we are close to the Midpoint Review stage.

@mengA6 mengA6 mentioned this issue Jun 18, 2024
Closed
8 tasks
@CherylEvans
Copy link
Contributor

CherylEvans commented Jun 20, 2024 •
edited
Loading

@mengA6
GM, Mike. I am working on tomorrow’s Midpoint Review and can’t access the Figma files. It says I don’t have access. I sent a request ticket for access, but it hasn’t come through yet. Is there any way you can change the permissions on the Figma files so I can access them and complete my review?

@mengA6
Copy link
Contributor Author

mengA6 commented Jun 20, 2024 via email

@erinrwhite erinrwhite added the midpoint-review Collaboration Cycle Midpoint Review label Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cc-kickoff collaboration-cycle For VSP Collaboration Cycle requests and improvements DBEX-TREX Disability Benefits Experience - Team T-Rex disability-experience midpoint-review Collaboration Cycle Midpoint Review sitewide CAIA
Projects
None yet
Milestone
Collaboration Cycle for [Disability B...
Development

No branches or pull requests
3 participants
@erinrwhite @CherylEvans @mengA6