Organization Chart
The
organization chart is the
management
work product consisting of
a diagram that documents the composition structure of an
organization or team.
The typical objectives of an organization chart are to
formally document the composition of the development:
- Organization in terms of its component teams, key roles,
and the aggregation (or reporting) relationships between
them.
- Team in terms of its component teams and the aggregation
(or reporting) relationships between them.
The typical benefits of an organization chart include:
- Enabling stakeholders to understand the:
- Composition of the development organization (or
team).
- Relationships between various teams.
- Their place within it.
An organization chart typically has the following
contents:
- Labeled boxes representing the teams or roles (possibly
also labeled with current membership)
- Arcs between boxes representing aggregation and/or
reporting relationships between the boxes
- Date drawn
An organization chart typically has the following
stakeholders:
- Producer:
- Evaluators:
- Approvers:
- Maintainers:
- Users:
An organization chart is typically produced and maintained
during the following phases:
An organization chart can typically be started if the
following preconditions hold:
An organization chart typically has the following
inputs:
- Work Products:
- Stakeholders:
- Organization charts must be regularly maintained because
they will otherwise quickly go obsolete.
- Simple drawing tools can help improve the
understandability of the chart.
- Use the procedure in the associated work flow to produce
this work product.
- If you tailor this work product, then tailor its
associated standard and inspection checklist.
Organization charts are typically constrained by the
following conventions:
-
Work Flow
-
Content and Format Standard
-
Inspection Checklist
-
Example Organization Chart