Collaboration Cycle Kickoff [cedar-1095b, Form 1095-B]

[JordanSWhite]

Steps to complete the Collaboration Cycle Kickoff

VFS Product Manager

• [x] Create this issue and notify the Collaboration Cycle team of this ticket in the in #vfs-platform-support (see Slack Workflow (User guide).
• [x] Answer the questions below and attach any artifacts you have available.
• [ ] Close this ticket when kickoff is complete and Platform has provided the recommended touchpoints.

Platform

• [x] Review the responses and comment in ticket with recommended touchpoints and practice area involvement.
• [x] Platform: Add project to the Platform Collaboration Point Tracker.

Artifacts (if available)

Provide links or documents for the following:

• Draft of product outline
• Wireframes, mockups, or prototypes
• Any other artifacts you have so far

Questions

Please refer to the guidance in Getting Started with the Collaboration Cycle for detailed information and examples for the below questions.

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

• [x] Yes
• [ ] No

2. Is your work a new product or an iteration to an existing product?

• [x] New
• [ ] Iteration

3. If this is an iteration, please tell us what product or feature you're iterating.

Product or feature: ____

4. Are you making changes to the visual design?

• [x] Yes
• [ ] No

5. Are you doing research with VA.gov users?

• [x] Yes
• [ ] No

6. Will your work involve changes to: (select all that apply)

• [ ] Tools and applications*
• [x] Static pages
• [ ] Both

For tools and applications, take into account if any static page entry points will need updates.

7. Will your work include:

• [x] New content
• [x] Changes to existing content

8. Are you making a change to the user flow?

• [x] Yes
• [ ] No

9. Are you making a change to urls, navigation, or entry points?

• [x] Yes
• [ ] No

10. Does your product or feature have Google Analytics tracking and a KPI dashboard in Domo?

• [ ] Yes
• [x] No

11. If yes, do you need to capture any other analytics or metrics in addition to what you're currently tracking?

• [ ] Yes
• [ ] No

12. Is there a GitHub label in the va.gov-team repo for this product?

• [ ] No.
• [x] Yes. Please specify: ____

13. Who is the VA business owner for this body of work?

• [x] VHA (Veterans Health Administration)
• [ ] VBA (Veterans Benefits Administration)
• [ ] NCA (National Cemetery Administration)
• [ ] VACO (Veterans Affairs Central Office)
• [ ] Other. Please specify: ____

Additional information

Please refer to the Platform Collaboration Cycle guidance on Platform website for more information about the Collaboration Cycle. FYI: @shiragoodman , @chaseakirby

[shiragoodman]

hey @JordanSWhite - could you please update the ticket title to include your team name and product/feature name?

[JordanSWhite]

@shiragoodman Sorry, thought I'd fixed that earlier. Now it's fixed for sure.

[shiragoodman]

Hi @JordanSWhite. Thanks for completing this Collaboration Cycle Kickoff ticket! Based on your responses, your project is a new tool and/or application (forms aren't typically considered static pages, however the entry point to the form will most likely be a static page) so we are recommending the following Collaboration Cycle touchpoints:

• Design Intent
• Research Plan Review
• Analytics Request
• Midpoint Review
• Contact Center Review
• Staging Review
• Privacy, Security, Infrastructure Readiness Review

Post Launch:

• Full Accessibility and 508 Office Audit
• Post-launch Check-in

We recommend that you bring the tool/application and static pages through the Collaboration Cycle together so we can review the full flow/user experience. (FYI the static page will likely be the entry point to the form, and you'll need to work with Sitewide Content on that. Please be sure to submit a Sitewide Content and IA Intake request).

Please reach out to Dave Conlon to let him know your work will impact static pages, the nature of the work, and your projected timeline.

The following practice areas will be included throughout the Collaboration Cycle process:

• Design
• Content
• Information Architecture (IA)
• Quality Assurance (QA)
• Accessibility
• Product

We understand that scope of work and/or solutions can change as you work through your design process. If you find that your scope and/or solution changes, please reach out so that we can update and/or modify your touchpoints appropriately.

Your project has been added to the Platform Collaboration Point Tracker. When you’re ready to schedule your recommended Collaboration Cycle touchpoints, please review the guidance outlined on the Collaboration Cycle Touchpoints page.

Also @JordanSWhite - please let me know what github label you use for your team. If you don't use one, we'll have to create one. Same thing for the 1095b product.