Overview
Assignment groups will be more closely aligned with organizational structure. We are moving away from cross-functional, product-based, and split teams. In TeamDynamix, technicians will belong to only one team. Managers may have multiple teams in situations where they manage two distinct groups with differing roles, responsibilities, skills, etc.
This new direction will:
-
Improve staff’s ability to easily identify work assigned or requested, whether it is related to incidents, service requests, RFCs, problems, or projects.
-
Improve a supervisor’s ability to identify work trends and improvements when/where needed, whether it is related to incidents, service requests, RFCs, problems, or projects.
-
Improve visibility into accountability and reporting.
-
Reduce complexity to escalation and work management between and within groups.
Details
Group Names
Group names will be built from the following components
-
“IT”: to signify this is an IT team within the TeamDynamix ecosystem.
-
“PFW”, “PNW”, “PWL”: to be used only for groups that are associated to one campus.
-
Multi-part group name: This will be the group’s descriptive identifier. Typically, multiple words will be separated by an “_”. Managers can request changes to this component.
Each of the above three component pieces will be in all caps and separated by an “_”.
Examples:
-
IT_PFW_DESKTOP_SUPPORT
-
IT_PNW_DESKTOP
-
IT_PWL_ESS_SUPPORT
-
IT_IDENTITY_MGMT
-
IT_MASS_STORAGE
-
IT_MESSAGING
Group Configurations
To assist tier 1 teams with escalation of tickets to the correct groups., escalation Instructions should be updated or created. Those instructions combined with the capability to add descriptions of functions or products a group supports to TeamDynamix. Other tier 2/3 teams could also benefit from access to this information and guidance.
Still need help? Click the 'Purdue IT Request' button to start a ticket.