...
Note |
---|
Minimum data needed:
|
Information / Data Category | Source and approach | Data needed |
---|---|---|
People and supervisory datastructure | HRIS → integrate with TeamForm (goal) | Minimum: Name , employee (First, Last and Preferred), Employee account name / ID, job Job title, supervisory Supervisory org name/ID, manager’s employee ID, FTE, Email address Additional useful fields: Employee Band , worker type, job family, contract end date, skills/job architecture Email address supervisory org ID Rate card (cost per day per role) Leave types Cross Functional Teams data(e.g. rank / level) Employee Cost Centre Employee Legal Entity / Employer Employee work location (e.g. building, city, country of place of work) Employee type (e.g. employee, contractor, vendor / supplier) Role family or job architecture Employment details (e.g. start / end date) Absence data (e.g. long term leave such as sabbatical / parental leave / military leave) Blended Rate card (e.g. average cost of a person by reporting line by day) [often a Finance provided data set] |
Cross-functional Teaming structure | Usually spreadsheets → replace with TeamForm (goal) | Minimum:
Also useful:
|
Capability / Skills data | HRIS or Skills Management → integrate with TeamForm | Useful if available:
|
Additional source systems / data types
Job requisitions / vacancy (e.g. for role approval and hiring status in a team) [Source System: Application Tracking System]
Team work items (e.g. epics that team is working on) [Source System: Work Management tooling such as Jira, Rally, AgilePlace (formerly LeanKit), Monday etc.]
Outcomes / Objectives e.g. Goals, OKRs for the organisation and the teams [Source System: Strategy / OKR tooling such as MS Viva Goals, Tability, Workboard, PlanView, Clarity, Jira Align etc.]