Overview
Understanding a few core concepts will help you navigate SEOP, make better decisions about your delivery model, and get value from the platform faster.
Concept 1: Orchestration
Orchestration is the central idea behind SEOP. Rather than managing engineers, tools, and processes as separate concerns, orchestration coordinates them as a unified system.
In practice, this means:
- Engineers are matched, deployed, and managed within a structured framework — not handed off and left unsupported
- Tools (Jira, GitHub, Slack, etc.) are connected to a common data layer, so performance data flows automatically into your dashboards
- Delivery processes (sprint planning, QA, code review, releases) follow consistent patterns across all engagements, regardless of team size or location
- AI Agents augment human work at defined points in the delivery cycle, reducing manual overhead and improving speed
Concept 2: Delivery Models
Scrums.com offers three core delivery models, each suited to different organisational needs:
Staff Augmentation — Individual engineers embedded into your existing team. You manage them day-to-day; Scrums.com handles everything else.
Dedicated Teams (DDT) — A full, assembled squad (2–6+ engineers) that operates as an extension of your engineering organisation, governed through SEOP.
Managed Delivery — Scrums.com takes fractional ownership of specific delivery outcomes (QA, product development, or platform maintenance) through a subscription service.
Each model can be combined. For example, you might run a Dedicated Team for your core product and use Staff Augmentation to fill specific skill gaps.
Concept 3: Subscription Tiers
Your subscription tier determines which platform features, governance controls, and support services you can access. Think of it as the operating level at which SEOP runs for your organisation.
- Standard — Core access for smaller teams getting started
- Recommended — Full orchestration for growing engineering organisations
- Enterprise — Maximum governance for large, regulated businesses
Concept 4: Talent Seats vs. Hours vs. Blocks
Scrums.com offers three ways to structure engineering capacity:
Seats (monthly subscription) — A full-time engineer for up to 160 hours/month, billed at a fixed rate. Predictable cost, maximum continuity.
Hours (time and materials) — Billed per approved hour worked. Suitable for variable workloads or ad hoc tasks.
Blocks (prepaid) — Pre-purchased packages of 40, 80, or 160 hours. Ideal for defined, time-boxed pieces of work.
Concept 5: On Demand Solutions (ODS)
On Demand Solutions are fixed-scope, time-boxed engagements that deliver a specific outcome — a code audit, architecture sprint, prototyping engagement, or security review — without requiring an ongoing subscription.
Each ODS comes in three tiers: Foundation, Expansion, and Comprehensive, reflecting the scope and depth of the deliverable.
Concept 6: AI Agents
AI Agents are automated processes deployed within SEOP to augment engineering work. They operate within defined boundaries — governed by your subscription tier and configured by your Enablement Partner.
AI Agents do not replace engineers. They eliminate low-value manual work so engineers can focus on building.Last modified on March 12, 2026
