Loading content/handbook/engineering/ai/workflow-catalog/_index.md +32 −0 Original line number Diff line number Diff line Loading @@ -120,6 +120,38 @@ which means our engineers will need to contribute directly to that codebase in p | [Shekhar Patnaik](https://gitlab.com/shekharpatnaik) / [Igor Drozdov](https://gitlab.com/igor.drozdov) | Duo Chat agent integration | | [Sebastian Rehm](https://gitlab.com/bastirehm) | Engineering Manager, backup contact for any of the above | ### ~Deliverable label The `~Deliverable` label is used to identify issues that the team has committed to deliver within a specific milestone. 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 #### Who applies it and when The Engineering Manager applies the `~Deliverable` label during the planning process before the start of an iteration. This decision is made in collaboration with the Product Manager based on: * Team capacity for the iteration * Issue estimates and complexity * Strategic priorities and customer commitments #### Prioritization Issues with the `~Deliverable` label take priority over other work in the iteration. 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 3. Consult with the Engineering Manager if priorities are unclear or if a `~Deliverable` issue needs to be deprioritized **During the iteration:** * 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 ### Our tech stack * GraphQL [backend](https://docs.gitlab.com/development/api_graphql_styleguide/) and Loading Loading
content/handbook/engineering/ai/workflow-catalog/_index.md +32 −0 Original line number Diff line number Diff line Loading @@ -120,6 +120,38 @@ which means our engineers will need to contribute directly to that codebase in p | [Shekhar Patnaik](https://gitlab.com/shekharpatnaik) / [Igor Drozdov](https://gitlab.com/igor.drozdov) | Duo Chat agent integration | | [Sebastian Rehm](https://gitlab.com/bastirehm) | Engineering Manager, backup contact for any of the above | ### ~Deliverable label The `~Deliverable` label is used to identify issues that the team has committed to deliver within a specific milestone. 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 #### Who applies it and when The Engineering Manager applies the `~Deliverable` label during the planning process before the start of an iteration. This decision is made in collaboration with the Product Manager based on: * Team capacity for the iteration * Issue estimates and complexity * Strategic priorities and customer commitments #### Prioritization Issues with the `~Deliverable` label take priority over other work in the iteration. 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 3. Consult with the Engineering Manager if priorities are unclear or if a `~Deliverable` issue needs to be deprioritized **During the iteration:** * 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 ### Our tech stack * GraphQL [backend](https://docs.gitlab.com/development/api_graphql_styleguide/) and Loading
