Document CAIA process for Governance visibility

[shiragoodman]

User Story

As a Governance team member, I want to be aware of when a VFS team is working with CAIA or not so that I know how to handle any upcoming touchpoints with the VFS team.

Assignee: @allison0034 Peer Reviewer: @KKitagawa-Bosch

Description

Governance has received guidance from CAIA on how they will inform us if they are working with a VFS team for a particular Collaboration Cycle initiative or not. Please see below:

Sitewide-CAIA label pulls CC Request tickets into CAIA board CAIA reviews CC Request swimlane weekly with Danielle If CAIA needs to be involved, CAIA will link the CC Request to existing product EPIC on our board (if there's no existing product EPIC, we create one) CAIA will add CAIA-Collab label to CC intake and remove Sitewide-CAIA label so they no longer appear on our board (that way we mark which intakes we're involved with, but our CC Request swimlane doesn't overflow with intakes) For CC Requests that don't need CAIA involvement, we just remove the Sitewide-CAIA label Proceed as usual, schedule kickoff if necessary, etc.

The above process needs to be documented and made visible to Governance team for their awareness. The purpose of this ticket is to document the process and determine where in the Collaboration Cycle guidance/documentation this process should live.

In addition, this ticket will also determine if this process, or aspects of it, should be documented elsewhere for greater visibility with OCTO-DE and VFS teams. Please document your recommendations for Governance team to review.

Impacted Artifacts

Live pages

Drafted pages

Tasks

• [ ] Placeholder task

Peer Review

To be completed by peer reviewer

• [ ] User story and acceptance criteria are met

Acceptance Criteria

• [ ] We have documented the process for determining if a team is working with CAIA in the Collaboration Cycle operational space on Confluence.
• [ ] We have written recommendations for where this process should also be shared with VFS teams, OCTO and/or others.

Team Notification

• [ ] 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

[allison0034]

This will move into the next sprint. My priorities were moved to an MVP for the new po sync