Add operational guidance around how to provide feedback to VFS teams with OCTO representation

[sterkenburgsara]

User Story

As a governance team member, I want to have clarity on how I should respond in collaboration cycle touchpoints to VFS teams with OCTO representatives, so that I meet expectations while maintaining positive relationships.

Assignee: Peer Reviewer:

Description

In a governance team sync with @humancompanion-usds on 5/2/2023, we discussed some feedback from Kevin Hoffman around how our team should provide feedback within the collaboration cycle to VFS teams with OCTO subject matter expertise and representation.

From the conversation, we should build into our guidance that it is acceptable to recuse ourselves from feedback if issues have already been directly addressed by OCTO representatives, or to defer to their judgment. We need to have platform-facing guidance around this so that we can point those teams to our approach and level-set expectations.

Impacted Artifacts

Internal documentation:

• How to provide feedback for Design Intent
• How to provide feedback for Midpoint Review
• How to provide feedback for staging review Platform website:
• Relevent pages in collaboration cycle section on Platform Website

Tasks

• [ ] Write up content block that describes our approach to providing feedback to teams with OCTO representation
• [ ] Run by @humancompanion-usds
• [ ] Add to appropriate documentation/guidance

Peer Review

To be completed by peer reviewer

• [ ] User story and acceptance criteria are met

Acceptance Criteria

• [ ] Governance team and VFS teams can both view and understand our approach to giving feedback to teams with OCTO representation

How to prepare this issue

Refinement

• [x] Ticket has user story, description, tasks, and acceptance criteria
• [ ] Ticket has additional appropriate labels, if applicable
• [ ] 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]

moving this to the backlog. Plan to discuss with @humancompanion-usds at next Governance sync

[shiragoodman]

This ticket was discussed at Governance team refinement in January 2024. The work has been determined to be no longer relevant to the team. Closing.

[shiragoodman]

Shira and Matt discussed on 2/9. Will take a 2nd look at the 1st task, "Write up content block that describes our approach to providing feedback to teams with OCTO representation" - will discuss at next team refinement.