|GitLab Team Handle||
|Team Boards||Team Board & Priority Board|
The Engineering Productivity team increases productivity of GitLab team members and contributors by shortening feedback loops and improving workflow efficiency for GitLab projects. The team uses a quantified approach to identify improvements and measure results of changes.
Enable frequent and positive experience of Community Contributions from the Wider GitLab Community.
The Engineering Productivity team focuses on the following workstreams and the associated Epics with workstream specific vision and objectives.
|~"ep::pipeline"||GitLab Project Pipeline Improvement
GitLab Project Selective Test Execution
|~"ep::review-apps"||Improve Review Apps Reliability
Improve Review Apps setup and usefulness
|~"ep::metrics"||Centralized handbook first metrics dashboard|
|~"ep::workflow"||Reviewer Roulette Improvements
|Kyle Wiebers||Backend Engineering Manager, Engineering Productivity|
|Rémy Coutable||Staff Backend Engineer, Engineering Productivity|
|Mark Fletcher||Backend Engineer, Engineering Productivity|
|Jen-Shin Lin||Senior Backend Engineer, Engineering Productivity|
|Albert Salim||Senior Backend Engineer, Engineering Productivity|
The Engineering Productivity team uses modified prioritization and planning guidelines for targeting work within a Milestone.
The Engineering Productivity team creates metrics in the following sources to aid in operational reporting.
The Engineering Productivity team will make changes which can create notification spikes or new behavior for GitLab contributors. The team will follow these guidelines in the spirit of GitLab's Internal Communication Guidelines.
Pipeline changes that have the potential to have an impact on the GitLab.com infrastructure should follow the Change Management process.
Pipeline changes that meet the following criteria must follow the Criticality 3 process:
These kind of changes led to production issues in the past.
The team will communicate significant pipeline changes to
#development in Slack and the Engineering Week in Review.
Pipeline changes that meet the following criteria will be communicated:
Other pipeline changes will be communicated based on the team's discretion.
Be sure to give a heads-up to
#ux Slack channels
and the Engineering week in review when an automation is expected to triage more
than 50 notifications or change policies that a large stakeholder group use (e.g. team-triage report).