VFS teams rely on the guidance provided in the Collaboration Cycle Request gh ticket for how to schedule, prepare and respond to touchpoints in the Collaboration Cycle. The challenge with this is that the guidance in the ticket is subject to change, and has changed. In the past, we have not updated active/open tickets, which has caused confusion for VFS teams who attempt to follow outdated and incorrect guidance.
For the upcoming changes to our scheduling workflow, @it-harrison wrote a script that will replace the old scheduling guidance with the new scheduling guidance for all open Collab Cycle Request tickets. See ticket #84495. Since it is likely that the guidance in the ticket will change again, Governance team wants to save the script for future use. The purpose of this ticket is to document in the Governance 'Team Guidance' space on Confluence details of the script so that we may modify and use it again, if/when needed.
Impacted Artifacts
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
User Story
"As a (persona), I (want to), (so that)."
Assignee: Peer Reviewer:
Description
VFS teams rely on the guidance provided in the Collaboration Cycle Request gh ticket for how to schedule, prepare and respond to touchpoints in the Collaboration Cycle. The challenge with this is that the guidance in the ticket is subject to change, and has changed. In the past, we have not updated active/open tickets, which has caused confusion for VFS teams who attempt to follow outdated and incorrect guidance.
For the upcoming changes to our scheduling workflow, @it-harrison wrote a script that will replace the old scheduling guidance with the new scheduling guidance for all open Collab Cycle Request tickets. See ticket #84495. Since it is likely that the guidance in the ticket will change again, Governance team wants to save the script for future use. The purpose of this ticket is to document in the Governance 'Team Guidance' space on Confluence details of the script so that we may modify and use it again, if/when needed.
Impacted Artifacts
Tasks
Peer Review
To be completed by peer reviewer
Acceptance Criteria
Team Notification
How to prepare this issue
Refinement
Planning
If this ticket is picked up from the Backlog mid-sprint, connect with Shira to ensure the below items are completed correctly