TeamForm can be used to implement a range of enables all operating models and organisational frameworks as outlined here https://www.teamform.co/solutions-for-teams .
TeamForm has a feature called principles, which can be used These design guidelines manifest themselves as organisational design principles, typically created by the organisation as guardrails when transitioning to, or as part of, cross-functional, agile or lean ways of working methods.
Teamform TeamForm has some predefined principles grouped into principle sets that can be configured to meet a particular use casemeasure. Principle Multiple principle sets can be created to accommodate different team archetypes (e.g. cross-functional, flow-to-work, service, platform, etc). Custom principle sets can also be createdFurther, where predefined principles are insufficient, as part of a client engagement, TeamForm Services can be engaged to create custom principle sets.
Examples of principles and principle sets include (outlined in more detail below):
...
Principles sets are defined via Settings / Principle sets using a JSON file.
...
The key fields referenced in a principle set are as follows:
“id” - a unique id string.
”name” - a name for this principle set (string)
“suitableGroupTypes”: a single team type (e.g. “squad” or a list of team types e.g. “squad”, “tribe”, “COE”
Under definitions, the
Default principle sets can be defined Principle sets are then chosen per team type via Settings / Org Structure type config. Select a team type, then choose a preferred principle set for that team type.
...
Should consist of between ${minMembers} and ${maxMembers} direct members.
...
Total Member Count
parameter maxMembers
title Should consist of no more than ${maxMembers} direct and indirect members.
...
Spread
parameter maxTeamsPerMember, teamType
title Each member should be in no more than {maxTeamsPerMember} teams.
...
Role Spread
parameter role, roleDisplayName, limit, teamType, teamDisplayname
title ${roleDisplayName} should work in no more than ${limit} {teamTypeDisplayName}
Code Block |
---|
{
"type": "ROLE_SPREAD",
"args": {
"role": "(.*product.*owner)",
"roleDisplayName": "Product Owner",
"limit": 1,
"teamTypeDisplayName": "Agile Team",
"teamType": "(group|team)"
}
} |
Ownership
parameter maxTeamsPerMember, teamType
...
consist of between 1 and ${limit} ${ownershipRoleDisplayName}.
...
.
...
Locality
parameter maxLocations
title Where teams are distributed it will be across no more than ${maxLocations} premises
...
...
{
"type": "LOCALITY",
"args": {
"maxLocations": 1
}
}
Line Manager Count
parameter maxManagers
title Team should have no more than ${maxManagers} line managers.
...
Role Diversity
parameter requiredRolesmaxTeamsPerMember, teamType
title Each team should have ${minCount}{Role}
...
member should be in no more than {maxTeamsPerMember} teams.
Total Role Diversity
parameter requiredRoles
title Team should be cross-functional and include the following capabilities:${requiredRoles}
Code Block |
---|
{
"type": "TOTAL_ROLE_DIVERSITY",
"args": {
"requiredRoles": [
{
"role": "Data Technician",
"minCount": 1
},
{
"role": "Field Technician",
"minCount": 1
},
{
"role": "Field Engineer",
"minCount": 3
},
{
"role": "Electrical Engineer",
"minCount": 3
}
]
}
} |
Same City Co-located
parameter null
...
Should consist of between ${minTeams} and ${maxTeams} direct ${subGroupName}.
Code Block |
---|
{
"type": "CHILD_TEAM_COUNT",
"args": {
"maxTeams": 15,
"minTeams": 1
}
} |
Direct Workforce Count
parameter minCount, companyNames
...
title Members geographically distributed should have at least <${goodOverlap} overlapped working hours.
...
Related articles
Filter by label (Content by label) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Page Properties | ||||
---|---|---|---|---|
| ||||
|
...