Manage split to Access and Measure
As stages expand, our approach has been to split them into groups. On Manage, we have two groups planned: Control and Framework.
You can see what these two teams are responsible for here.
Manage is currently 1 backend EM, 4 backend, 1 frontend EM, 5 frontend, and 2 UX. With @valexieva joining Manage, we'll also have 2 PMs. If we split the team at this level of staffing, we'd get two groups:
|Access (current)||Measure (current)||Access (plan)||Measure (plan)|
|1 shared backend EM||1 shared backend EM||1 backend EM||1 backend EM|
|2 BE||2 BE||5 BE||4 BE|
|1 shared frontend EM||1 shared frontend EM||1 frontend EM||1 frontend EM|
|2 FE||3 FE||2 FE||4 FE|
|1 UX||1 UX||1 UX||1 UX|
|1 PM||1 PM||1 PM||1 PM|
|1 TAE||1 TAE||? TAE||? TAE|
From a staffing perspective, the biggest gaps are in engineering management and backend ICs.
Side note: I've also proposed a 3rd group in this MR.
If we think that staffing levels are sufficient to plan for a group split, we should consider the timeline for splitting into the two groups. It's getting close to the 1st, so we'll need to get 12.0 finalized in the next couple of weeks. We can consider a couple of routes:
- Split into 2 groups for 12.0. Access and Measure would have separate boards, meetings, and would operate independently.
- Split into 2 groups for 12.1. Continue planning as a single Manage team for 12.0. Label planned issues by group using ~"group:measure" and ~"group:access" labels.