Collaboration Cycle Kickoff [Identity, Sign-in Modal]

[nsoutouras]

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
• [x] Wireframes, mockups, or [prototypes] (https://www.figma.com/proto/5HXJL69PLSGNujaQEQyY8Q/Login.gov---UX2?node-id=154%3A2&scaling=min-zoom&page-id=0%3A1&starting-point-node-id=159%3A123)
• [ ] 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?

• [ ] New
• [x] Iteration

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

Product or feature: VA.gov Sign-in Modal

4. Are you making changes to the visual design?

• [x] Yes X
• [ ] No

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

• [x] Yes X
• [ ] No

Usability Testing

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

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

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

7. Will your work include:

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

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

• [ ] Yes
• [x] No X

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

• [ ] Yes
• [x] No X

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

• [ ] Yes
• [x] No X

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

• [ ] Yes
• [ ] No

12. Does your team have a Github label for this product?

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

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

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

Additional information

Please refer to the Platform Collaboration Cycle guidance on Platform website for more information about the Collaboration Cycle.

[peggygannon]

Thanks @nsoutouras for completing this Collaboration Cycle Kickoff ticket! Based on your responses, your product is an iteration to a tool and/or application So we are recommending the following Collaboration Cycle touchpoints:

• Design Intent
• Research Plan Review
• Midpoint Review
• Contact Center Review
• Staging Review
• Privacy and Security Review
• Full Accessibility and 508 Office Audit
• Post-launch Check-in

Also, since this work impacts static pages, please be sure to work with the sitewide content team on any content updates.

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. Please review the guidance at Collaboration Cycle Touchpoints for information on each touchpoint.

cc @APorter-Clarity