Workforce Planning

Pre-requisites: At a minimum, Team Directory is live and includes:

People structure (e.g. from your HRIS / HCM system): the line management hierarchy of people participating in cross-functional teams
- Principal Role or Capability
- Hatted Roles (if used)
- Skills (if used)
- Managers of people who can support participation in a cross-functional team (aka Chapter lead / Capability lead)
Demand Teaming Structure
- Delivery teams, organised in a way that makes “sense” to people in the org
  - Tribe → Squad
  - Business Unit → Domain → Subdomain → Squad
  - Portfolio → System Release Train → Agile Release Train → Agile Team

These are the building blocks that create a foundation for workforce planning.

Ideally, there should be a clear separation between supply and demand structures
Additionally:
- an existing cadenced planning approach (eg Quarterly Business Review)
- the appetite to enrich planning with a workforce lens

Nice to haves, that can be added later. TeamForm encourages progress over perfection.

View of the high level work that demand teaming structures are doing, eg:
- Strategic Outcomes / OKRs / Initiatives / Epics (for example)
Some simple rules / guides for team composition e.g. min / max size, role composition etc.)
Blended rates for the people supply groupings
An understanding of funding approach, funding sources and how it links to teams

Want to get started sooner?

TeamForm offers an interactive Miro board you can use to visualise the Structure, Strategy and work for your organisation. Get started here: https://miro.com/miroverse/strategy-to-execution-map/