Role: System Administrator |
|
|
This role maintains the development infrastructure, both hardware and software. This includes installation, configuration, backup, etc. |
Role Sets: Managers, Production & Support |
|
Relationships
|
Modifies |
|
Process Usage |
|
Main Description
An individual taking on the role of System
Administrator needs a good understanding of the specific hardware and software components used on a project, and
the possible dependencies between these components.
|
Staffing
Skills |
In-depth knowledge of the development platform's operating system(s), network, and mechanisms, such as security and
distribution, is required. Problem solving and fault diagnosis are also key skills for this role.
|
Assignment Approaches |
The System Administrator role can be
assigned in the following ways:
-
Assign one or more staff members to perform the System Administrator role exclusively. This is a commonly adopted
approach and is particularly suitable for large teams or where smaller teams will "time-share" centralized
administration resource.
-
Time-share a pool of System
Administrator resources across multiple projects. This is another common approach used in large organizations
in which an IT department is resourced separately from-and the resources "leased" back to-each development project.
-
Assign one staff member to perform the System Administrator role in conjunction with another technical
role such as the Implementer or Integrator role. This approach is suitable for small to medium sized teams,
although it often results in reduced productivity in the both role assignments which you will need to allow for.
-
Assign each team member in the development team responsibility for their own administration tasks. While this
approach can be suitable for smaller teams, this will detract from focusing on other tasks, and often results in
lost efficiency through duplicate effort.
|
More Information
© Copyright IBM Corp. 1987, 2006. All Rights Reserved.
|
|