Build a diverse and global development team to support and drive results across the section, while maintaining our values and unique way of working.
Drive results through iterative development as we add ModelOps and Anti-abuse features into the product. Our teams are data-driven, support dogfooding, and collaboration within GitLab and the wider community.
The following table shows who will provide cover if one or more of the Data-Science Engineering management team are unable to work for any reason.
|Team Member||Covered by||Escalation|
|Wayne Haber||Christopher Lefelhocz||Ashley Kramer|
|Phil Calder||Jay Swain||Wayne Haber|
|Jay Swain||Phil Calder||Wayne Haber|
|Monmayuri||Wayne Haber||Wayne Haber|
If an issue arises - such as a production incident or feature change lock - that a team member needs management support with when their direct manager is not online, the team member should reach out to any Data-Science Engineering Manager by mentioning in
#data-science-section. The manager can help the team member follow the process and co-ordinate to ensure the team member has the necessary support.
If an Engineer is unavailable the Engineering Manager will reassign open issues and merge requests to another engineer, preferably in the same group.
Some people management functions may require escalation or delegation, such as Workday and Navan Expense.
This can be used as the basis for a business continuity plan (BCP), as well as a general guide to Data Science Engineering continuity in the event of one or more team members being unavailable for any reason.
(Sisense↗) We also track our backlog of issues, including past due security and infradev issues, and total open SUS-impacting issues and bugs.
(Sisense↗) MR Type labels help us report what we're working on to industry analysts in a way that's consistent across the engineering department. The dashboard below shows the trend of MR Types over time and a list of merged MRs.