Explore potential ways for Governance to initiate the workflow for DI, MPR, and SR

[shiragoodman]

User Story

As a Governance team member, I want to explore possibilities for how the Slack workflow is initiated with VFS teams so that we can weigh our options and decide to implement that solution that meets our needs.

Assignee: @briandeconinck Peer Reviewer: @allison0034

Description

In ticket #83511, Governance team proposed 3 different solutions for how we might be notified that a VFS team has scheduled a DI, MPR and/or SR in Calendly. At the weekly initiative meeting on 6/10, the team expressed a preference for a solution that posted to the #platform-governance-team channel rather than DMs --- meaning, either the Google Calendar solution or the Calendly email-to-channel solution. Subsequent testing determined that emails to the channel were the most viable option.

Now that the team has decided how they'd like to be notified, Governance team must determine how to kickoff the workflow with the VFS team and what the new process will look like. We need to decide what responsibilities fall on Governance team (and when) as well as what responsibilities fall on VFS team (and when). It would be helpful to document a user flow with both Governance and VFS responsibilities defined. Ideally, the solutions for DI, MPR, asynch MPR and SR will be the same with content being the only difference.

Similarly to ticket #83511, the purpose of this ticket is to propose a solution, however we will not be implementing the solution within this ticket. That will take place afterwards in a separate ticket.

Impacted Artifacts

Tasks

• [x] Document a proposed flow of how Governance will kick off the workflow on the VFS team Slack channel
  • Potential workflow triggers for DI, MPR, and SR scheduling
• [x] Define how the content would differ for DI, MPR, asynch MPR and SR
  • Addressed in document
• [x] After peer review, share with Governance team for their feedback and input

Peer Review

To be completed by peer reviewer

• [x] User story and acceptance criteria are met

Acceptance Criteria

• [x] We have proposed a new flow for how to initiate the Slack workflow for DI, MPR, asynch MPR and SR

Team Notification

• [x] Slack post on #platform-governance-team
• [ ] Presentation at Weekly Initiative Meeting
• [ ] No notification needed

How to prepare this issue

Refinement

• [x] Ticket has user story, description, tasks, and acceptance criteria
• [x] Ticket has been sized
• [x] Once all above items are checked, add the 'Ready' label.

  Planning

  If this ticket is picked up from the Backlog mid-sprint, connect with Shira to ensure the below items are completed correctly

• [x] Ticket has been discussed as a team at Planning
• [x] Ticket has been assigned to appropriate initiative or quarterly epic
• [x] Ticket has been assigned to a Sprint
• [x] Ticket has been moved to the Planned pipeline in the Governance team board
• [x] Ticket as an assignee and peer reviewer

[briandeconinck]

End-of-sprint update: Should have the work done by end of day today, but might not be done with enough time for @allison0034 to be able to PR. With the holiday tomorrow, this may carry over into the start of the next sprint. cc @shiragoodman

[allison0034]

@briandeconinck just wanted to check in, is this ready for review?

[shiragoodman]

@briandeconinck could you please also update the Description with the solution we chose? ty!

[briandeconinck]

Ready for PR @allison0034 if I can catch you before your PTO!

[allison0034]

Peer review complete... share away!

[shiragoodman]

Goal is to review this in the Weekly Initiative Meeting on 7/1 with the full team.

Update 6/26: See @briandeconinck's comment below. We will be moving forward with the emoji reaction option.

[briandeconinck]

Update after discussion in Slack: Emoji reaction option was resoundingly endorsed by Governance team members in the office this week. Per @shiragoodman in Slack, we'll be moving forward with that option. Outcome documented in Confluence, closing out this ticket!