An organization archetype is a typical example of an organizational setup. In our case, we are specifically interested in organization archetypes relevant to how the organization might engage with GitLab. We've learned that roles of various personas change based on the specific organizational setup of their company. This handbook page captures the organization archetype we have identified.
An organization archetype can be considered an additional layer to an end-user's demographics alongside personas. When collecting insights during interviews, it would be useful to understand the context of the user within their role and organization via organization archetypes.
Cloud infrastructure enables flexible and purposefully designed infrastructure per application. Because of this, infrastructure provisioning and software development has become part of a coupled workflow. We have observed 5 different types of infra team or platform team models outlined below.
All-in-One teams use resources democratically. In this model, developers are also DevOps engineers. They have access and credentials to infrastructure and related toolings and are expected to use them as needed. There may be unofficial specialist that teammates go to for help.
Company Size: SMB
Examples of how resources are used:
On Service Model teams, infrastructure teams gate access to and are responsible for optimize the use of resources. Other development are customers of the infrastructure team and have to request resources and ask for help when needed.
Company Size: Mid-Market, Enterprise
Examples of how resources are used:
On service & embedded teams, resource use is guided or optimized in partnership. Teams buddyup with specialist as needed so that both Dev and Ops are working together.
Company Size: SMB, Small Enterprise
Examples of how resources are used:
On All-in-One & Service teams, specialized roles guide/enforce DevOps/SecOps practice. Within development teams, they have the access to many of the resources. Central platform teams provide tools to facilitate self-service and enforce governance and compliance.
Company Size: Large Enterprise
Examples of how resources are used:
On All-in-One & Embedded teams, DevOps engineer work embedded within product groups or product lines to co-create DevOps/SecOps practice relevant to the users.
Company Size: Large Enterprise
Examples of how resources are used: