@@ -54,3 +54,16 @@ We default to working inline with the [GitLab values](/handbook/values/), by fol
-**Group Reviews:** We review project status asynchronously every Wednesday to ensure alignment ahead of the Production Engineering group review.
-**Retrospectives:** A team-level retrospective issue is created regularly to reflect on our processes and encourage a culture of continuous improvement.
-**On-Call:** Most team members participate in the on-call rotation as part of our commitment to the reliability of the infrastructure we own.
### Infradev Workflow
We use the following workflow to triage [infradev](/handbook/engineering/workflow/#infradev) issues assigned to Fleet Management. This workflow is proposed and we expect to iterate on it as we learn what works.
1.**Auto-assignment in triage state:** When a new infradev issue is routed to our team, [triage-ops](https://gitlab.com/gitlab-org/quality/triage-ops) automatically assigns every team member to the issue, signaling it is in the triage state.
2.**Collaborative triage:** Anyone on the team can triage the issue. The goal is to confirm:
1. The issue makes sense and has enough context to act on.
1. Fleet Management is the right team to own it.
1. The priority label is appropriate.
1. The due date is realistic.
3.**Ready for work:** Once the issue passes triage, we unassign all team members and apply the `~"workflow-infra::ready"` label to move it into the ready queue.
4.**Pulling from the ready queue:** Team members pull from the ready queue as capacity allows. When a due date is approaching, a bot may randomly assign an issue to a team member to ensure nothing slips.
