| Table of Contents | ||
|---|---|---|
|
What is Team Directory?
Refer to this document to understand what Team Directory is and what challenges it is designed to help solve for: at the heart of creating a single source of truth for teams and team members, is it the foundation to build upon for people, teams, strategy, outcomes, work and much more! More info on the parent page Team Directory
Team Directory roll out approach
...
Customised tenant established with SSO sign in
People and demand teams exist in TeamForm
TeamForm is the source of truth for delivery structures
Gain insights on team composition and capacity availability
Data enrichment for more up to date team composition, capacity availability insights and employee engagement surveys
Area | Activity |
SSO configured as per (Single Sign On) configured to your organisation’s preference solution Standard SSO role based assess access defined and implemented | |
People Import | Manual CSV import of people (HRIS) data brought into TeamForm
|
First iteration of delivery team structures represented in TeamForm(often making something visible, prompts clarifications and changes). | |
People assignment to delivery teams | People are in delivery team structures People memberships have been validated by key stakeholders Process to membership updates have been designed, signed off and embedded with the objective that TeamForm is the source of truth for delivery structures. |
Data Availability | Real-time team & people data CSV extract |
...
Area | Activity |
|---|---|
Delivery Team Structures | All delivery team structures and types are validated, improved where necessary and are continuously maintained in TeamForm Optional: Delivery teams have team description and linkages to their work tracking board (where possible) such as Jira boards and company strategy/objectives |
People Import (i.e supply structure) | Automated file transfer of people (HRIS) data brought into TeamForm, with additional data fields such as:
|
Other data integration | Additional data sets brought into TeamForm from external systems via data integrations:
|
Visualisation and linkage of other data set | Where available if there are job titles that are not equivalent to someone’s role titles, the roles are reflected using tags Another typical example is funding source from your finance system. |
Additional data source of truth in TeamForm | All additional data sources where TeamForm is the source of truth for have been brought into the platform. Examples include platform ownership, assets, funding sources, etc |
Reporting | TeamForm data is connected into the organisation’s data lake or reporting BI tool |
Secondary supply structure (by exception when needed) | Secondary supply structures brought into TeamForm |
...
Benefit(s) of bringing the data into TeamForm | |
Associations | Users can see the interdependencies between teams, codify interaction patterns such as Team Topologies, and show where teams share the same leader |
Employee images | Enhanced user experience especially if your organisation has a virtual working environment as it allows users to know who they are speaking with |
Ways of working principles | Giving TeamForm all your team archetypes from the start will allow you to:
|
Optional additional foundational set up for further TeamForm use case
There are additional data elements that need to be set up in Directory if you would like to use TeamForm’s advance use cases.
See Also:
| Child pages (Children Display) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|