Implement team yaml enhancements to include borrow, primary and secondary priority of engineering team members

Exec Summary

The challenge as it stands now, team.yml contains important information that is needed for R&D investments planning

1. https://internal.gitlab.com/handbook/product/investment/ shows the ratio of engineers/PMs invested in each product area and is what our CProdO uses regularly
2. https://about.gitlab.com/handbook/product/categories/ shows the assignment of R&D personnel
3. Our requirements not only include borrow information but also 1st and 2nd work priorities assigned. There is still a need to maintain team.yml from R&D

I’d like to iterate in a way that we can leverage workday and still provide the missing information needed for our FY25 long range planning.

Current status 2023-08-16

• Implementation is complete
• Instructions for Engineering Managers+ to update the yaml file are in Engineering Leaders to update team yaml file wi... (#34464 - closed)

Objective

The objective of this task is to update the "team yaml" file by including borrows and capturing per engineer first and second/partial assignments. This update requires the engineering manager or team lead's involvement.

1. Update yaml file to including the following information for team members
   1. Borrow to which team (optional field)
   2. First assignment
   3. Second/partial assignment
   4. Assignments are controlled list, there will be a CI job that checks the validity of assignments to match a certain list
2. Show the update information in the internal org chart and team page?
   1. https://comp-calculator.gitlab.net/org_chart
   2. https://about.gitlab.com/company/team/
3. This will also keep our categories page up-to-date
   1. https://about.gitlab.com/handbook/product/categories

Alignment with Workday

It is helpful to call out that we are very supportive of aligning this enhancement with Workday. As I vocalised in the video recording. Key points:

1. We want this enhancement to co-exist with workday
2. We prefer that job title specialty is regular synced from workday to yaml
3. We prefer that reporting structure is regular synced from workday to yaml
4. Borrow will work on top of existing data from workday
5. If needed we can help the people-ops team push changes in team yaml back to workday via API calls and scripts.

Overview video https://www.youtube.com/watch?v=8BboA-5ym_c

New yaml fields

borrow: 
  to: EM_NAME
  end_date: yyyy-mm-dd
work_priorities:
  -  
  - 

Mock

Handbook org chart	HTML (rough draft)

Plan

Iterations

• 1st Iteration
  • Add support for the following 2 fields in the team yaml file
    • borrow.to if exists refer to an existing team member (this case will be using the manager).
    • work_priorities numbered list of work priority
  • Danger CI job to ensure:
    • borrow.to if exists refer to an existing team member.
    • work_priorities if exists is an array containing only recognized values.
  • A work priority yaml file:
    • A controlled list of items
  • Export team member data in CSV:
    • https://about.gitlab.com/handbook/engineering/team.csv
    • https://about.gitlab.com/handbook/product/team.csv
    • https://about.gitlab.com/handbook/security/team.csv
  • The following pages to show the new fields:
    • https://comp-calculator.gitlab.net/org_chart
• 2nd Iteration
  • The following pages to show the new fields:
    • https://about.gitlab.com/company/team/
    • https://about.gitlab.com/handbook/product/categories