Q2 Epic Company Operating Model Epic that we contribute to: https://gitlab.com/groups/gitlab-operating-model/-/work_items/816+ Current roadmap: https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/developer-experience/development-analytics/#next-fy27-q1q2 ### Background GitLab is undergoing a fundamental shift in how software gets built. The **Modular Features** initiative is reshaping the platform architecture, while **agentic development** is accelerating the pace of code production to levels previously unseen. This velocity creates both opportunity and challenge for the teams responsible for platform health and observability. **CI Health** remains a critical foundation for this new reality. As AI agents generate code at machine speed, the stability of our default branch and the reliability of our pipelines continue to directly impact developer velocity across the organization. Flaky tests, infrastructure failures, and broken pipeline incidents create compounding delays when pipelines are running at scale. The the goal is prevention, not just measurement. Development Analytics sits at the intersection of these initiatives. Our work on **CI Health tooling and reporting** provides the observability layer that teams need to ship confidently at speed. Our collaboration with **Modular Features** teams ensures that new architectural patterns are instrumented from day one. As Performance Enablement articulates in their [Q2 direction](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/work_items/4350): the goal is to make quality visible to the developer, with zero cognitive load, zero friction, and zero extra steps. Development Analytics contributes to this vision by ensuring CI health signals surface in the workflows developers already use. Q2 focuses on deepening these integrations: advancing Test Health Error Budgets, iterating on CI Health incident reporting, and supporting the Modular Features teams (Artifact Registry, Knowledge Graph, Auth) as they build the next generation of GitLab's platform. ### Items For Q2 <table> <tr> <th>Issue/Epic</th> <th>Area</th> <th>DRIs</th> <th>Reported as part of Operating Model?</th> </tr> <tr> <td> https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/work_items/4363+ \+ a new Epic to cover the creation of a standard set of dashboards </td> <td> https://gitlab.com/groups/gitlab-operating-model/-/work_items/1009+ </td> <td> `@ichernikov` </td> <td>Yes</td> </tr> <tr> <td> https://gitlab.com/groups/gitlab-org/quality/analytics/-/work_items/44+ </td> <td> CI Health https://gitlab.com/groups/gitlab-operating-model/-/work_items/1009+ </td> <td> `@acunskis` </td> <td>Yes</td> </tr> <tr> <td> https://gitlab.com/groups/gitlab-org/quality/analytics/-/work_items/46+ </td> <td>CI Health</td> <td> `@richard.chong` </td> <td>Yes</td> </tr> <tr> <td> https://gitlab.com/groups/gitlab-org/quality/analytics/-/work_items/48+ </td> <td> https://gitlab.com/groups/gitlab-operating-model/-/work_items/1011+ </td> <td></td> <td>Yes</td> </tr> <tr> <td> https://gitlab.com/groups/gitlab-org/quality/analytics/-/epics/47+ </td> <td>CI Health</td> <td></td> <td>No</td> </tr> <tr> <td> https://gitlab.com/groups/gitlab-org/quality/analytics/-/work_items/49+ </td> <td> https://gitlab.com/groups/gitlab-operating-model/-/work_items/1009+ </td> <td></td> <td></td> </tr> <tr> <td> https://gitlab.com/groups/gitlab-org/quality/-/work_items/409+ </td> <td>Observability</td> <td> `@ichernikov` </td> <td></td> </tr> </table> ### Items for Q3 | Issue/Epic | Area | DRI | Reported as part of operating model | |------------|------|-----|-------------------------------------| | https://gitlab.com/groups/gitlab-org/quality/-/work_items/403+ | CI Health | | | | https://gitlab.com/groups/gitlab-org/quality/analytics/-/epics/45+ | CI Health | | |