Overview
Talent is one of the four catalog primitives. It covers every way Scrums.com supplies people to your delivery. The primitive has three shapes. They share one vetting, contracting, onboarding and matching model. They differ in what unit you receive and who manages it day to day.
Billing Model: Subscription / Hourly / Seat / Block
Delivery Model: Scrums-managed / Client-managed
Projects are invoiced on the 1st of every month. Hourly engagements include a quarterly reconciliation — unused billed hours are credited and any shortfall is invoiced. See Billing & Usage for full terms.
Choosing a shape
Ask what the gap is.- Capacity or a specific skill on a team that already works → Individual Experts.
- A whole unit of delivery you do not want to build or run → Dedicated Teams.
- Direction, governance or technical leadership → CXO Network.
CXO Network is not yet documented here. Speak to your Enablement Partner, or see Support & Contact.
How Matching Works
When you request a team member or team, SEOP’s AI-assisted matching system evaluates candidates against:- Technical requirements — Stack, seniority, specialisation (e.g. React, Python, AWS, Kubernetes)
- Timezone compatibility — Overlap with your core team’s working hours
- Delivery model fit — Experience with your preferred methodology (Scrum, Kanban, SAFe)
- Industry context — Familiarity with regulated sectors (FinTech, Banking, Healthcare) where relevant
Scaling Teams
Teams can be scaled up or down on a monthly basis. Common scaling scenarios include:- Adding a specialist role (e.g. DevOps Engineer) for a migration sprint
- Increasing engineering headcount ahead of a major release
- Reducing team size after a product launch
- Swapping roles as tech stack requirements shift
Related
- Catalog Overview — how the primitives are organised
- AI-Assisted Vetting & Matching
- Deployments — how a Talent engagement is tracked