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

# What's included

> What a Delivery Plan covers, what is billed as catalog usage, and the delivery guarantees that apply.

## Coverage

Every Delivery Plan covers the full lifecycle of the work in your backlog:

* Discovery, planning and scoping
* UX/UI design and architecture
* Backend, API and frontend engineering
* Integrations
* QA, including AI code review
* DevOps and release engineering, including zero-downtime deployment where your pipeline and architecture support it
* Security and compliance work
* Maintenance after launch

One accountable **delivery owner** runs the engineers, designers and testers on your plan. You do not contract, onboard or manage individuals.

Delivery runs inside your existing architecture, pipeline and release process. Where those constrain what is achievable — a deployment model that cannot release without downtime, an environment that cannot be reproduced, a release gate outside your control — your delivery owner will say so during scoping and, if you want it changed, raise the work to change it. Improving the pipeline is itself deliverable work on the plan.

## Scopes

Every scope in the [scope library](https://www.scrums.com/ai-development/scopes) is included in your plan.

Adding a scope does not change your monthly price. It is delivered from your prioritised backlog by the same team, within the same workstream capacity. What determines cost is how many months of delivery your backlog needs, not which scopes are in it.

Work that does not match a published scope is scoped from scratch on the same terms.

## Tiers

| | **Core** | **Factory** |
| - | - | - |
| Active workstreams | One | Multiple |
| Backlog | Unlimited | Unlimited |
| Delivery owner | One | One |
| Coverage | All disciplines | All disciplines |
| Scopes | All | All |
| Price | Published monthly rate | Scales with the number of workstreams |

You buy monthly delivery capacity, not a fixed project price. Billed monthly, excluding VAT or sales tax. Current rates are on the [Delivery Plans page](https://www.scrums.com/ai-development#pricing); additional parallel workstreams require additional capacity, so the Factory tier is priced per engagement.

## Guarantees

| Commitment | Terms |
| - | - |
| **First code in 48 hours** | Your team is connected to your repositories and writing code within 48 hours of access being granted. |
| **First deliverable in 14 days** | Your first agreed deliverable ships within 14 days of scope and access being confirmed, or your first month is free. |

Both clocks start when scope is confirmed and access to repositories, cloud accounts and CI is granted — not at checkout. The first deliverable is agreed in writing before the clock starts, and the guarantee applies to the first deliverable on a new plan. See [Starting your plan](https://www.scrums.com/docs/ai-development/starting-your-plan.md) and the [full terms](https://www.scrums.com/legal/terms-and-conditions).

## Included every month

* **\$500 in AI infrastructure catalog credits** in your first month.
* Live delivery tracking in the platform: board, epics, decisions, risks and the deployed log.
* Monthly delivery reporting against your backlog.

## Annual plans

Annual commitments include **\$10,000 in specialist services**:

* A technical assessment of your existing systems
* A delivery roadmap
* CI/CD pipeline setup

## What is not in the plan

Delivery work is covered. These sit outside it:

* **Infrastructure usage** — your cloud estate, and AI infrastructure or agent runtime deployed from the [AI Catalog](https://www.scrums.com/docs/catalog/overview.md) beyond your included credits. This is consumption, not delivery work.
* **Third-party services** — licences, subscriptions and vendor fees for the tools your product depends on.
* **Engineers you manage directly** — see [Hire](https://www.scrums.com/docs/hire/overview.md).

You own all code and IP produced on the plan. See [IP Ownership](https://www.scrums.com/docs/security/ip-ownership.md).


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