Update product group capacity (#30491)

This commit is contained in:
Luke Heath 2025-07-01 16:53:51 -06:00 committed by GitHub
parent 5fa2550614
commit eb4bc8f331
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -29,7 +29,7 @@ At Fleet, [anyone can contribute](https://fleetdm.com/handbook/company#openness)
| Product group | Goal _(value for customers and/or community)_ | Capacity |
|:-----------------------------------------|:-----------------------------------------------------------------------------------------------------------------------|:---------|
| [MDM](#mdm-group) | Increase and exceed maturity in the [device management](https://fleetdm.com/device-management) product category. | 104 |
| [Orchestration](#orchestration-group) | Increase and exceed maturity in the [orchestration](https://fleetdm.com/orchestration) product category. | 117 |
| [Orchestration](#orchestration-group) | Increase and exceed maturity in the [orchestration](https://fleetdm.com/orchestration) product category. | 143 |
| [Software](#software-group) | Increase and exceed maturity in the [software management](https://fleetdm.com/software-management) product category. | 104 |
\* The number of [estimated story points](https://fleetdm.com/handbook/company/communications#estimation-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.