Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Area

Activity

Security access, authentication & authorisation

SSO configured as per your organisation’s preference

Standard SSO role based assess defined and implemented

People Import

Manual CSV import of people (HRIS) data brought into TeamForm

  • Employee ID

  • Job Title

  • Direct Manager

Delivery Team Structures

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
Basic prototype reporting through Redash

...

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 Jira 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:

  • Cost Centre

  • Skills or Job Family

  • Optional: vacancies, leave, contract end dates…

Other data integration

Additional data sets brought into TeamForm from external systems via data integrations:

  • Strategy/OKRs (eg: PlanView, Clarity)

  • Work items (eg: Jira, Rally)

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:

  1. Put people into the right team types that resonate with them

  2. Allow users to easily create new teams of the specified team types in TeamForm

Optional: Additional foundational set up for further TeamForm use cases

We understand that every organisation is at a different maturity level and has different priorities therefore not all users will see the need to use all or any of TeamForm’s additional functionalities. However in the event that you do wish to explore the use of other additional TeamForm features, please use the table below to help you understand what extra data is required to be brought into the platform in order to unlock the full potentials in each of the TeamForm functionality use cases.

...

Advance TeamForm Use Cases

...

Workforce Planning

...

Short & long term workforce forecast

...

Org Design

...

Assess team structures against principles

...

Manage & cost OKRs

...

Financials

...

Blended rate cards based on your supply hierarchy so that as you are planning or designing a team, users can get a high level estimation of what the team will cost

...

Status
colourYellow
titleoptional

(tick)

...

Status
colourYellow
titleoptional

(tick)

...

Status
colourYellow
titleoptional

(tick)

...

Status
colourYellow
titleoptional

(tick)

...

Secondary supply structure (only consider if it’s a must required)

...

This information is critical to setting up the right process flow to how work demands can be triaged and approved from demand through to supply leads.

...

(tick)

...

(tick)

...

(tick)

...

(tick)

...

Tracking of data accuracy

...

Data accuracy is key for a successful roll out and adoption of TeamForm as users can focus on what the data is telling them knowing they can trust what they see rather than fixing the data so that it resonates with them. We can provide you a dashboard to help you monitor the data accuracy, making it easy for leaders to know what specifics they need to fix in TeamForm.

...

(tick)

...

(tick)

...

(tick)

...

(tick)

...

(tick)

...

Employees' leave/holiday info

...

If not brought into TeamForm, it will impact:

  1. The supply leaders' decision making during workforce planning to know who they can allocate against demand requests

  2. Difficult for people in the organisation to know who is or isn’t around the team

...

(tick)

...

(tick)

...

Vacancies

...

If not brought into TeamForm, it will hinder the supply leaders' accurate view of how many roles they have available to meet demand requests.

However, when vacancies are brought into TeamForm, you need to consider how the vacancy management process is going to be for users as TeamForm do not support the traditional HR functionalities in managing the lifecycle of vacant roles.

...

(tick)

...

(tick)

...

(tick)

...

Status
colourYellow
titleOptional

(tick)

...

Secondments

...

If not brought into TeamForm, it will impact:

  1. The supply leaders' decision making during workforce planning to know who they can allocate against demand requests

  2. Difficult for users to trace back to why there were certain people movements within the team for a specific period of team

...

(tick)

...

(tick)

...

(tick)

...

Status
colourYellow
titleOptional

(tick)

see also:

...

See Also:

Child pages (Children Display)
depth1
allChildrentrue
style
first0
sortAndReverse