Explore potential ways for Governance to initiate the workflow for kickoff

[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: @erinrwhite

Description

In ticket #84493, we reestablished the GitHub integration notification on our #platform-governance-team Slack channel for when a new gh ticket is opened with the CC-Request label. This will ideally serve as the trigger for Governance beginning the Collaboration Cycle Kickoff workflow. However, since the current kickoff workflow begins with the VFS team initiating the workflow on their team channel, the workflow will have to be reconfigured with Governance team being responsible for beginning the flow.

The purpose of this ticket is to define the new process for kickoff. Per ticket #84492, which is a comparable ticket for redefining the DI, MPR and SR workflows, "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." The kickoff workflow can differ from the others bc it does have a different trigger (gh integration message) opposed to DI, MPR and SR (Calendly email notification on Slack).

Impacted Artifacts

Tasks

• [x] Document a proposed flow of how Governance will kick off the workflow on the VFS team Slack channel
  • Potential workflow trigger for Collab Cycle kickoffs
• [ ] 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 kickoff

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]

@erinrwhite quick and easy one, ready for peer review when you get back!

Potential workflow trigger for Collab Cycle kickoffs

[shiragoodman]

@briandeconinck I added a couple comments - looks good! I think in Erin's absence, you can move forward and share this with the rest of the team (aka Ian).

[shiragoodman]

@briandeconinck I think we can do the same thing here that we did for #84492. Let's move forward with the emoji response. No need for Erin to review - I will fill the role as peer reviewer. Please update the doc like you did for the other ticket with the decision. LMK if you have any questions!

[briandeconinck]

Document updated, closing this as complete!