Determine operational impact of PO Sync to other touchpoints

[shiragoodman]

User Story

"As a (persona), I (want to), (so that)."

Assignee: Peer Reviewer:

Description

What details are necessary for understanding the specific work or request tracked by this issue? Note: we need to update our documentation to check that a PO Sync has been scheduled before they can attend any other touchpoint.

adding checks to our scheduling docs for DI, MPR and SR to ensure that the PO Sync occurred.

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

• [ ] Placeholder AC

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]

ticket has been moved out of PO Sync initiative and into tech debt