Collaboration Cycle Kickoff [Virtual Agent]

[katieho-va]

Steps to complete Collaboration Cycle Kickoff

• [x] VFS Product Manager (@sham009): Create this issue and fill in your team and feature name in the title.
• [x] VFS: Answer the questions below.
• [x] VFS: Link to this issue once created in vfs-platform-support in Slack; tag @vsp-product-support-members.
• [x] VFS: Attach any available artifacts.
• [x] VSP: Review the responses and comment in ticket with recommended touchpoints and practice area involvement.
• [ ] VSP: Add project/feature to the Platform Collaboration Point Tracker.
• [ ] VFS: Close this ticket when all steps above are completed.

Artifacts (if available)

• Link to draft of product outline
• Link to wireframes, mockups, or prototypes

Questions

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

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

• [x] Yes
• [ ] No

Is your work a new product/feature or an iteration to an existing product/feature?

• [x] New
• [ ] Iteration

Will your work impact only static content pages?

• [ ] Yes
• [x] No

Are you making changes to the visual design?

• [x] Yes
• [ ] No

Are you making changes to content?

• [x] Yes
• [ ] No

Are you making a change to the user flow?

• [x] Yes
• [ ] No

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

• [x] Yes
• [ ] No We will have a unique URL for our bot (which lives on a standalone VA.gov page), but will not be changing navigation on the main VA site. The entrypoint to our page will depend on whether we use a toggle or banner as our means of launching our product to a small % of users.

Are you doing research with VA.gov users?

• [x] Yes
• [ ] No

Does your product/feature have Google Analytics tracking and a KPI dashboard in Domo?

• [ ] Yes
• [x] No We want to use Google Analytics to see interaction patterns on the VA site vs. users who click to engage with the bot. We’ll also have analytics from Power Virtual Agent, and no KPI dashboard. We will be using feature flags and only exposing the bot link to a subset of users.

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

• [ ] Yes
• [x] No

Additional information

Please refer to the VSP Collaboration Cycle README on Github for more information about the Collaboration Cycle.

[shiragoodman]

hey @katieho-va and @LucianaAlexanderMorais. We had an Orientation meeting this morning. I reviewed the Collaboration Cycle and various touchpoints, and Luciana walked me through the scope of the product and your planned POV launch.

We are recommending the following Collaboration Cycle touchpoints:

• Midpoint Review
• Analytics Request
• Privacy and Security Review
• Staging Review (TBD)

Information about scheduling touchpoints can be found here.

Please reach out if you have any questions!

[shefalinayak]

Hi @shiragoodman, which collab cycle touchpoints need to be completed before we enable our page in production (behind a feature toggle)? Since it's a new app on vets-website, we currently have it in dev/staging but excluded from va.gov prod, and we want to understand the timeline for updating that.

[shiragoodman]

hi @shefalinayak - I was under the impression that your product launch in June would be in Staging and you wouldn't be launching in production for your POV testing. Is that not still the case?

[katieho-va]

Hey @shiragoodman, we were actually planning to launch on VA.gov prod for the POV using the banner/toggles to show our product to a select % of users. However, this plan might change as we are currently in discussions with Microsoft about whether or not we can migrate our bot over to GCC preview for our intended launch date in June. We will re-comment on this ticket once we know more!

[shiragoodman]

ok thanks, @katieho-va. That would be helpful. To answer the earlier question from @shefalinayak, I posted the recommended Collaboration Cycle touchpoints as a comment on 4/14. Privacy & Security review is mandatory for any product launching on VA. gov. The Staging Review we had defined as TBD, based on available timing. If you have made significant changes to your product since the Midpoint Review on 4/22, then yes, I'd recommend a Staging Review. We request 4 days notice so we have adequate time to review, and we ask that teams complete their own foundational accessibility testing. If you'd like more info on this, please let me know.

[katieho-va]

Thanks @shiragoodman! FYI @LucianaAlexanderMorais