Difference between revisions of "Department"
m (Caretaker: Format cat links) |
m |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | <noinclude>{{glossary}}</noinclude>{{:organisational structure|Departments}}<noinclude> | |
| − | + | == See also == | |
| − | + | *[[System]] | |
| − | + | *[[Ontology]] | |
| − | + | *[[Role]] | |
| − | + | </noinclude> | |
| − | |||
Latest revision as of 01:40, 26 July 2011
|
Departments are used to define structure in a system which are, by default (i.e. the way the Platform specification defines organisational structure), divided into the following hierarchy,
- Organisation → Departments & Roles → Projects → Tasks
All of these structural aspects of an organisation can, like the organisation itself, be addressed and involved in workflow in the same way as a trust group, or member of a trust group. In fact every concept (node) in the Ontology is a trust group that has members and a direction it's evolving towards.
This structure can change according to the needs of specific groups, for example, an individual member or project will most likely not require separate departments. And in some cases there can be more appropriate words for the structural categories, for example, in the context of Self organisation, the category that's normally called a "department" is called "area of focus". Groups can use splitting & merging processes to change the granularity or diversity of an operating system "in the field".
