|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.
This metric captures how many Merge Requests are merged into customer facing projects divided by the number of product team members.
Customer facing projects are projects which would come with an installation of GitLab. The current list can be found with all the projects identified in the
projects_part_of_product.csv file in the
Product team member is defined as all non-VP or Director role in Development, UX, Quality, and Product Management.
With this measure, there is a preference towards adding new projects into the existing product. In the event that a new GitLab project is included in the product that a customer would receive then please open an issue on the quality team tasks project.
Within the issue, please add details on how this project is included with an Omnibus or Cloud Native installation of GitLab for consideration by the Engineering Productivity team. The team will evaluate the request and make any updates to charts and metrics in the sources listed above.
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.
The team will communicate 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).