Versions Compared

Old Version 6

changes.mady.by.user Space Sync for Confluence

Saved on

compared with

New Version Current

changes.mady.by.user Space Sync for Confluence

Saved on

Key

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

...

Note

Minimum data needed:

  • supervisory structure aka line management structure [source system: HRIS / HRMS such as Workday, SAP Success Factors, Oracle Fusion HCM]

  • cross functional teaming structure [source system: often a spreadsheet]

Information / Data Category

Source and approach

Data needed

People and supervisory datastructure

HRIS → integrate with TeamForm (goal)

Minimum:

  • Employee Name

, employee ID, job title, supervisory org name, manager’s employee ID, FTE

  • (First, Last, Preferred)

  • Employee account name / ID

  • Job title

  • Supervisory Org Name / ID

  • Supervisor / Manager Name / ID

  • FTE (Full Time Equivalent e.g. full time / part time for available 0-1)

  • 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 Avatar / Profile pic

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

  • Teams and team types
    (e.g. squads/crews, missions/domains/tribes)

  • Team of Teams / Value Stream Hierarchy

Also useful:

  • Team relationships / associations

  • Team design rules / guardrails (e.g. min / max size of team, role composition etc.)

  • Team Descriptions / Key Links (backlog / wiki pages)

  • Team cost centre / cost object

  • Team role aka “Hatted roles” e.g. Product Owner, Scrum Master

  • Additional attributes e.g. IT Asset

Capability / Skills data

HRIS or Skills Management → integrate with TeamForm

Useful if available:

  • List of skills

  • Skills mapped to individuals

  • Skills with other attributes (E.g. capability or job family)

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.]