> ## 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.

> ## Agent Instructions
> Scrums.com is the enterprise AI platform for software engineering. SEOP, the Enterprise AI Software Engineering Orchestration Platform, is the architecture of the platform: one control plane for AI agents, models, engineers and infrastructure.
> Write the entity name as Scrums.com. Never write the bare word Scrums.
> Platform capabilities are documented under /platform. Delivery Plans (under /ai-development) and Hire Engineers are documented under Platform Services. The AI Catalog is documented under /catalog. Each docs page links to its page on https://www.scrums.com.

# Choosing a delivery model

> Delivery Plans or Hire — how to pick the right starting point for your situation.

Scrums.com delivers engineering two ways. **Delivery Plans** give you managed delivery capacity: you queue work, Scrums.com ships it. **Hire** gives you engineers — individuals or a full team — who work inside your organisation under your direction.

The dividing line is ownership. If you want an outcome delivered, take a Delivery Plan. If you want engineering capacity you direct yourself, hire.

## Start here

| Need | Best starting point | Day-to-day ownership |
| - | - | - |
| "We need this built, and we don't want to run it." | [Delivery Plan](https://www.scrums.com/docs/ai-development.md) | Scrums.com |
| "We have a team. We're short one specialist." | [Hire — individual engineers](https://www.scrums.com/docs/hire/staff-augmentation.md) | You |
| "We have a roadmap and no bandwidth, but we want to run the team." | [Hire — dedicated team](https://www.scrums.com/docs/hire/teams.md) | You |
| "We need someone to keep this running — uptime, patching, support." | Delivery Plan with a managed SLA scope | Scrums.com |
| "We need QA on every release, but not a QA hire." | Delivery Plan with a QA scope | Scrums.com |
| "Our delivery is broken and we're not sure what we need." | Delivery Plan, starting with a discovery scope | Scrums.com |

A **scope** is a pre-defined piece of delivery work you add to your plan backlog — a new feature, an old framework upgrade, a new platform, or ongoing operations under a service level. Scopes are included in your plan at every tier. Browse them at [scrums.com/ai-development/scopes](https://www.scrums.com/ai-development/scopes).

The two models are not exclusive. Many clients run a Delivery Plan alongside engineers they manage themselves; our team can help you determine what's best for you, just reach out via [chat or email](https://www.scrums.com/docs/resources/support.md).

## Next

* [Delivery Plans](https://www.scrums.com/docs/ai-development.md) — how managed delivery works
* [Hire](https://www.scrums.com/docs/hire/overview.md) — engineers and teams you direct


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.