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: Deployment surfaces
Scrums.com organizes deployable capacity and outcomes across three surfaces: AI Catalog — Agents, models, MCP servers, skills, APIs, and infrastructure. AI Development — Defined scopes and managed delivery owned by Scrums.com. Hire — Engineers and teams that add ongoing delivery capacity. You can combine deployments from these surfaces within one workspace.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.- Free — Browse and scope the platform and catalog
- Access — Deploy catalog records with standard governance
- Business — Add multi-team governance, intelligence, and API access
- Enterprise — Maximum governance for large, regulated businesses