Org structure defines the team hierarchy of the organisation. All HR systems have a hierarchical breakdown of the reporting line structure. TeamForm enables a matrix model of the org structure often known as cross functional teams. This means we allow an enterprise to be represented in both reporting lines and a team view of where people work.
...
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Info |
|---|
Org structures can also be referred to as:
Refer to TeamForm Glossary for standard definitions of commonly used words in TeamForm |
Below root, we typically create two group types of the organisation:
The
...
people or “supply” view
Represents the people reporting lines as typically shown in an HR system or capability groups such as Practice Area or Chapter where the organisation have adopted agile structures
We can also have conventional groupings like “Executive Team, Division, Sub-Division” in the hierarchy as well
TeamForm recommends that the People (Supply) structure replicates the HR system. This allows for easier ongoing data maintenance and consistency and an easier way to assign the correct decision maker during workforce planning.
The
...
work or “demand” view
Represents the cross functional teams oriented around work. This typically has terms like Squads, Agile Teams, Value Streams, Tribes, Platform Areas or Work Portfolios.
...
Org structures can also be referred to as:
org taxonomy
group types
team types
...
Rules for org structure
TeamForm enables you to establish rules associated with each team types, such as:
allowed parent types (e.g. a ‘Squad’ type must have a parent of type ‘Tribe’)
allowed children types (e.g. a ‘Chapter Area’ type can have children team types of ‘Chapter’)
Related information
| Filter by label (Content by label) | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|