> ## Documentation Index
> Fetch the complete documentation index at: https://www.scrums.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# How Scrums.com SEOP Works

> Understand how the SEOP platform coordinates teams, AI, and workflows to deliver software predictably.

## Overview

Software Engineering Orchestration Platform (SEOP) works by creating a structured, governed delivery environment around every engineering engagement. Rather than leaving clients to coordinate vendors, tools, and processes independently, SEOP provides a single operational layer that manages all three.

[View www.scrums.com/platform for more information](https://www.scrums.com/platform)

**Service Name:** [Scrums.com](https://www.scrums.com) Platform<br />**Billing Model:** Subscription<br />**Delivery Model**: Platform-delivered

## The Delivery Loop

Every engagement on SEOP follows a continuous delivery loop:

**Plan → Build → Measure → Improve**

1. **Plan** — Work is scoped, prioritised, and assigned. Sprints are structured with clear acceptance criteria. Risks are identified upfront.
2. **Build** — Engineers execute work within the platform. AI Agents assist with code review, automated testing, documentation, and workflow automation. Progress is tracked in real time.
3. **Measure** — SEOP continuously collects delivery data: velocity, DORA metrics, defect rates, cycle times, and team utilisation. These are surfaced in your Analytics dashboard.
4. **Improve** — AI-powered insights surface recommendations — flagging bottlenecks, suggesting workflow changes, and predicting delivery risks before they become problems.

## How Teams Are Deployed

When a new engagement begins, Scrums.com follows a structured deployment process:

1. **Discovery** — Your Enablement Partner works with you to understand your delivery model, tech stack, and immediate priorities.
2. **Matching** — The AI-assisted vetting system identifies the best-fit engineers from Scrums.com's pool of 10,000+ vetted professionals.
3. **Assembly** — Your team is assembled, briefed, and given access to your tools and workspace.
4. **Kickoff** — A formal kickoff call aligns everyone on goals, sprint cadence, and communication norms.
5. **Delivery** — Sprints begin. Progress is tracked in SEOP, with your Enablement Partner available for escalations.
6. **Review** — Quarterly Business Reviews (QBRs) on Recommended and Enterprise plans assess performance and align future delivery priorities.

## Risk & Change Management

### Risk Identification

SEOP's AI agents monitor sprint data continuously for risk signals, including:

* Sprint completion rates falling below 70%
* Increasing defect rates or PR rejection rates
* Team members with unexpectedly low utilisation
* Backlog items without estimates entering active sprints
* Deployment frequency declining over successive sprints

When a risk signal is detected, it is surfaced in the Dashboard and flagged to your Enablement Partner.

### Change Management

Scope changes are a normal part of software delivery. Scrums.com manages changes through a structured process:

1. **Change request raised** — Client or team identifies a scope change
2. **Impact assessment** — Enablement Partner assesses effort, timeline, and cost implications
3. **Approval** — Client approves or rejects the change
4. **Backlog update** — Approved changes are added to the backlog and estimated
5. **Delivery** — Changes are incorporated into the next available sprint

For significant scope changes (e.g. adding new product features mid-engagement), a revised Statement of Work (SOW) is issued.

## How AI Fits In

AI is embedded throughout SEOP. Key AI capabilities include:

* **AI QA Agents** — Automate regression testing, flag edge cases, and reduce defect escape rates
* **Delivery Analytics Agents** — Monitor sprint health and surface risks before they cause delays
* **Code Review Agents** — Review pull requests for quality, security, and standards compliance
* **Documentation Agents** — Generate and maintain technical documentation automatically
* **AI Agent Gateway** — A governed orchestration layer for deploying custom AI agents into your engineering pipelines, your own MCP environment

All AI activity is logged, auditable, and operates within defined governance boundaries. See [AI Agents](/docs/products/agents/overview) for full details.

## Governance by Tier

SEOP's governance controls scale with your plan:

| Feature             | Standard   | Recommended | Enterprise |
| ------------------- | ---------- | ----------- | ---------- |
| Delivery dashboards | Basic      | Advanced    | Custom     |
| AI agents           | Seat Based | Seat Based  | Seat Based |
| Audit logs          | —          | —           | ✓          |
| SSO/SAML            | —          | —           | ✓          |
| QBRs                | —          | Quarterly   | Executive  |
| Support SLA         | 24h        | 8h          | 4h         |

### Subscription Tiers 

View detail on Subscription tiers here:  [Pricing | Software Engineering Platform Plans](https://www.scrums.com/pricing)

### Overview

[Scrums.com](https://www.scrums.com) supports three core delivery models, each designed for different organisational contexts, levels of autonomy, and delivery goals. Most clients use a combination of models across different workstreams.

All delivery models operate within the SEOP platform, meaning you get the same governance, visibility, and AI augmentation regardless of which model you choose.

### The Three Models at a Glance

 

|                          | **Staff Augmentation**      | **Dedicated Teams**                                     | **Managed Delivery**                 |
| :----------------------- | :-------------------------- | :------------------------------------------------------ | :----------------------------------- |
| **Best for**             | Filling specific skill gaps | Scaling an engineering function                         | Outsourcing delivery outcomes        |
| **Who manages the team** | You                         | You (with [Scrums.com](https://www.scrums.com) support) | [Scrums.com](https://www.scrums.com) |
| **Team size**            | 1+ individuals              | 2–10+ engineers                                         | Fractional, as needed                |
| **Commitment**           | Monthly                     | Monthly subscription                                    | Monthly subscription                 |
| **Ramp time**            | 21 days                     | 21 days                                                 | 4 weeks                              |
| **Delivery governance**  | Light                       | Standard                                                | Full                                 |

### How to Choose

**Choose Staff Augmentation if:**

* You have an established engineering team and need to fill specific roles fast
* You want to retain full control over day-to-day work management
* You need flexibility to scale individuals up or down frequently

**Choose Dedicated Teams if:**

* You need a complete squad working exclusively on your product
* You want a team that operates like an in-house extension, not a vendor
* You are scaling a product roadmap and need consistent delivery

**Choose Managed Delivery if:**

* You want [Scrums.com](https://www.scrums.com) to take accountability for specific delivery outcomes
* You do not have the internal capacity to manage a team
* You need guaranteed throughput on QA, product development, or platform maintenance

> Not sure which model fits your situation? Your [Scrums.com](https://www.scrums.com) Enablement Partner will help you decide during the discovery phase.

 

All subscription models require an active [Scrums.com](https://www.scrums.com) platform subscription. Outcome Driven Sprints are available without a subscription and can be purchased as a standalone engagement. Speak to your Account Executive or Enablement Partner for pricing specific to your scope.