Commit eef37976 authored by Kenny Johnston's avatar Kenny Johnston 🌀

Clarify non-overlapping scope for groups

parent 47c8db54
Pipeline #76442100 passed with stages
in 25 minutes and 36 seconds
......@@ -42,10 +42,7 @@ The categories form a hierarchy:
and Defend to get the 10 (DevOps) **value stages**, and then add the Growth
and Enablement **team stages**. Values stages are what we all talk about in
our marketing.
1. **Group**: A stage has one or more [groups](/company/team/structure/#groups).
Each of the groups has a dedicated backend engineering team. Within shared
functions, like quality and product management, individuals are paired to one
or more stages so that there are stable counterparts.
1. **Group**: A stage has one or more [groups](/company/team/structure/#product-hierarchy-groups).
1. **Categories**: A group has one or more categories. Categories are high-level
capabilities that may be a standalone product at another company. e.g.
Portfolio Management. To the extent possible we should map categories to
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment