Add CAIA to existing Collaboration Cycle workflows

[shiragoodman]

User Story

As a CAIA team member, I want to be made aware of the products/features being brought to the Collaboration Cycle so that we can continue to explore how to merge our existing processes with Governance.

Assignee:
Peer Reviewer:

Description

Governance and CAIA PMs have been discussing how best to merge their existing processes so that VFS teams have a better experience working with both teams in the Collaboration Cycle. Before any drastic changes are made, CAIA and Governance PMs would prefer to start with small changes that give CAIA the visibility they need to provide support. The following changes will be made within this ticket by the Governance team:

• Add the CAIA team label sitewide-caia to the Collaboration Cycle Request YAML template
  • This will ensure CAIA has visibility of work coming through the Collaboration Cycle
• Remove CAIA code block from the Collaboration Cycle Kickoff operational process - aka Sitewide CAIA as a touchpoint will no longer be recommended within any Collaboration Cycle Request tickets
  • This will help VFS teams to no longer perceive CAIA as a touchpoint
  • This will help CAIA move away for their existing intake ticket
• Add link to the original Kickoff, Design Intent, Midpoint Review and/or Staging Review Slack workflow request thread (that took place on the VFS teams Slack channel) to the automated Slack message on the #platform-collaboration-cycle channel
  • This will help CAIA, Governance and the VFS team have an open communication channel (aka Slack thread) for discussing anything relevant to the work (Governance team already has this with the VFS)

Impacted Artifacts

Tasks

• Placeholder task

Peer Review

To be completed by peer reviewer

• User story and acceptance criteria are met

Acceptance Criteria

• CAIA is made aware of all new Collaboration Cycle Kickoffs
• VFS teams are no longer recommended to submit a CAIA intake via the Collaboration Cycle Request ticket
• All members of the #platform-collaboration-cycle channel are able to locate the VFS teams Slack request for the Collaboration Cycle touchpoint

Team Notification

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

How to prepare this issue

Refinement

• Ticket has user story, description, tasks, and acceptance criteria
• Ticket has been sized
• 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

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

[shiragoodman]

FYSA @coforma-terry @strelichl @eli-oat