Update Code Creation links to AI Coding

## Related Resources

- [Code Creation Product Categories](/handbook/product/categories/#code-creation-group)

- [AI Coding Product Categories](/handbook/product/categories/#ai-coding-group)

---

title: "How We Work"

description: "Working processes, communication practices, and operational procedures for the Code Creation group"

description: "Working processes, communication practices, and operational procedures for the AI Coding group"

---

## Introduction

    - Team members, regardless of their timezone, can review issues with the "workflow::refinement" label at their convenience

    - Use the issue comments for discussion and clarification. You may loop in other team members or domain experts from outside the team to provide further context and/or give feedback on a proposed solution.

    - Individual team members are encouraged to schedule regular, asynchronous backlog refinement sessions on their calendars

    - Use the [Code Creation Refinement Board](https://gitlab.com/groups/gitlab-org/-/boards/8994789) to make issues needing refinement easy to find

    - Use the [AI Coding Refinement Board](https://gitlab.com/groups/gitlab-org/-/boards/8994789) to make issues needing refinement easy to find

    - Make sure to timebox your refinement efforts. Remember that the goal of refinement is not to provide a detailed solution, but to provide clarity on the problem and to provide a starting point on the solution. See [Where to Draw the Line Between Refinement and Implementation](#where-to-draw-the-line-between-refinement-and-implementation).

4. Refinement Tasks:

    - Team members should focus on the following when refining an issue:

### What to Work on First: Deliverables

- **Priority**: Deliverables are considered the highest priority and should be completed before the end of the milestone, aligning with our iteration cycle and monthly release schedule.

- **Self-Assignment**: Engineers can pick any issue marked with the ["Deliverable" label](/handbook/product-development/how-we-work/product-development-flow/#required-statuses-1) and assign it to themselves, making these issues the top priority for the milestone. Issues for the current milestone can be found on the [Code Creation workflow board](https://gitlab.com/groups/gitlab-org/-/boards/5998095).

- **Self-Assignment**: Engineers can pick any issue marked with the ["Deliverable" label](/handbook/product-development/how-we-work/product-development-flow/#required-statuses-1) and assign it to themselves, making these issues the top priority for the milestone. Issues for the current milestone can be found on the [AI Coding workflow board](https://gitlab.com/groups/gitlab-org/-/boards/10081212).

- **Importance**: It's crucial for engineers to make a concerted effort to complete these deliverables within the cycle, and to promptly communicate any obstacles to their engineering manager.

- **Communication and Flexibility**: Unexpected challenges can arise, potentially impacting the completion of a deliverable. Early communication of these challenges allows for possible solutions, such as scope reduction or reassignment. If a deliverable cannot be completed within the cycle, it is moved to the next cycle for completion. This scenario is an opportunity for both the engineer and the engineering manager to reflect and learn from the experience.

## Matt Nohr's README

I'm an Engineering Manager at GitLab for the [AI Coding](/handbook/engineering/ai/ai-coding/) and [Context Systems](/handbook/engineering/ai/ai-coding/) teams.

I'm an Engineering Manager at GitLab for the [AI Coding](/handbook/engineering/ai/ai-coding/) team.

I've previously worked on these teams at GitLab:

- AI Engineering:Code Creation

- Ecosystem

- Create:Code Review

- Create:Editor

- Create:Knowledge

- Monitor:APM and Monitor:Health

- Ecosystem

- Monitor:Health

- Monitor:APM

My Links:

  - Answers the question "what section is this work supporting?"

- Stage label (ex: `devops::create`)

  - Answers the question "what stage is this work supporting?"

- Group label (ex: `group::code creation`)

- Group label (ex: `group::code review`)

  - Answers the question "what group is this work supporting?"

- Issue weight

- Iteration (once the issue is scheduled)