Update product group assignees (#13704)

The product group capacities is # of engineers * 13. #g-website seemed
way too high given it's just Eric, so I dropped that to 13. Note that
he's also being counted for 13 on the CX capacity, so we're
double-counting Eric.

His vuln dashboard work is tracked on the CX board, which is why we're
counting him there.
This commit is contained in:
Luke Heath 2023-09-12 13:26:21 -05:00 committed by GitHub
parent ec95b8fa7c
commit 647fc04907
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -16,10 +16,10 @@ At Fleet, [anyone can contribute](https://fleetdm.com/handbook/company#openness)
| Product group | Goal _(value for customers and/or community)_ | Capacity\* |
|:--------------------------|:--------------------------------------------------------------------|:-----------------|
| [MDM](#mdm-group) | Reach maturity in the "MDM" product category. | 75 |
| [Customer experience (CX)](#customer-experience-group) | Make customers happier and more successful. | 60 |
| [Infrastructure](#infrastructure-group) | Provide and support reliable and secure infrastructure. | 16 |
| [Website](#website-group) | Make the website wonderful. | 48 |
| [MDM](#mdm-group) | Reach maturity in the "MDM" product category. | 65 |
| [Customer experience (CX)](#customer-experience-group) | Make customers happier and more successful. | 65 |
| [Infrastructure](#infrastructure-group) | Provide and support reliable and secure infrastructure. | 13 |
| [Website](#website-group) | Make the website wonderful. | 13 |
\* The number of estimated story points this group can take on per-sprint under ideal circumstances, used as a baseline number for planning and prioritizing user stories for drafting. In reality, capacity will vary as engineers are on-call, out-of-office, filling in for other product groups, etc.