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

# Starting your plan

> From checkout to your first deliverable in production: what happens on day 0, what Scrums.com needs from you, and when each clock starts.

Onboarding begins at checkout. The delivery clocks begin when scope is confirmed and access is granted — usually the same day, but they are separate events, and the second is the one that counts.

## The sequence

| | Stage | What happens |
| - | - | - |
| **01** | Checkout | You pick a Delivery Plan. Your workspace is set up and Delivery Plans appears in the sidebar. |
| **02** | Scope confirmed | You and your delivery owner agree what the plan is working on first and what the first deliverable is. |
| **03** | Access granted | You connect repositories, cloud accounts and CI. **Day 0 — both clocks start here.** |
| **04** | First code | Within 48 hours, your team is connected and writing code against your repositories. |
| **05** | First deliverable | Within 14 days, your first agreed deliverable is in production. |
| **06** | Steady state | You queue requests; the team works the highest-priority one until it is live, then starts the next. |

## What Scrums.com needs from you

Delivery cannot start until these are in place. Preparing them before checkout is the single biggest lever on time-to-first-deliverable.

**Access**

* Source control — repository access with review and write permissions
* CI/CD — pipeline access and the ability to run a release
* Cloud accounts or hosting environments in scope
* Any app store, registry or third-party consoles the work touches

**Context**

* What the plan is working on first, and what "done" looks like for it
* Current architecture and known constraints
* Existing backlog, if you have one, to seed the board
* Who on your side makes product decisions and who reviews releases

**People**

* A named decision-maker. Requests flagged **needs your input** sit idle until someone on your side clears them.

See [Authentication & Access Control](https://www.scrums.com/docs/security/authentication.md) for how credentials are handled, and [Integrations](https://www.scrums.com/docs/integrations/integrations.md) for connecting your tools.

## Setting up your space

Delivery Plans are scoped to a **space**. A space is one plan's board — its backlog, its epics, its decisions and risks, and its deployed history. The space selector sits at the top of the board, alongside live counts for each stage.

A space holds your whole plan, not one stream of it. On **Factory**, the concurrent workstreams run inside the same space and against the same backlog, so priority is set once across all of them rather than negotiated between separate boards.

Invite your team from **Settings → Account**. Anyone with workspace access can raise requests, comment, and clear needs-input flags.

## Seeding the backlog

Before kickoff, add the work you already know about. Requests are free to raise and your backlog is unlimited — the constraint is the active workstream, not the queue.

Everything in the backlog stays editable until the team picks it up, so an imperfect first pass is useful. See [Making requests](https://www.scrums.com/docs/ai-development/requests.md).

## Kickoff

Your delivery owner runs kickoff once scope and access are confirmed. Kickoff sets:

* The first deliverable, named and recorded on the board
* Priority order for the opening backlog
* Release cadence and environments
* Review and approval expectations on your side
* Reporting cadence

From here, the board is the record. See [Tracking delivery](https://www.scrums.com/docs/ai-development/tracking-delivery.md).


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