| [Sebastian Rehm](https://gitlab.com/bastirehm) | Engineering Manager, backup contact for any of the above |
### Planning cadence
We plan and align our work to GitLab's [product milestones](/handbook/product/product-processes/milestones/). Milestone planning happens during the week before the start of the next milestone.
### ~Deliverable label
The `~Deliverable` label is used to identify issues that the team has committed to deliver within a specific milestone.
@@ -127,30 +131,30 @@ This label serves multiple purposes:
***Commitment signal**: Communicates to stakeholders and customers that we intend to complete this work in the milestone
***Prioritization**: Helps team members identify which issues should be worked on first
***Focus**: Clarifies which work is essential vs nice-to-have for the iteration
***Focus**: Clarifies which work is essential vs nice-to-have for the milestone
#### Who applies it and when
The Engineering Manager applies the `~Deliverable` label during the planning process before the start of an iteration.
The Engineering Manager applies the `~Deliverable` label during the planning process before the start of a milestone.
This decision is made in collaboration with the Product Manager based on:
* Team capacity for the iteration
* Team capacity for the milestone
* Issue estimates and complexity
* Strategic priorities and customer commitments
#### Prioritization
Issues with the `~Deliverable` label take priority over other work in the iteration.
Issues with the `~Deliverable` label take priority over other work in the milestone.
Team members should:
1. First, work on assigned `~Deliverable` issues in the current iteration
2. If all `~Deliverable` issues are complete or blocked, pick up other issues from the iteration
1. First, work on assigned `~Deliverable` issues in the current milestone
2. If all `~Deliverable` issues are complete or blocked, pick up other issues from the milestone
3. Consult with the Engineering Manager if priorities are unclear or if a `~Deliverable` issue needs to be deprioritized
**During the iteration:**
**During the milestone:**
* If a `~Deliverable` issue becomes blocked or cannot be completed, communicate this early in `#g_workflow_catalog` or the relevant issue
* The Engineering Manager may adjust `~Deliverable` labels during the iteration based on changing priorities or capacity
* The Engineering Manager may adjust `~Deliverable` labels during the milestone based on changing priorities or capacity
