The model
A plan buys one active workstream: one managed team working your highest-priority request until it is live, then starting the next. Your backlog is unlimited — the workstream is the constraint. More requests mean more months, not faster delivery. One plan covers every discipline. Web, mobile, backend, AI, data, QA, DevOps and design share the same backlog and the same team, so work does not need to be split across separate engagements.Delivery Plans walkthrough — request to live, 9 min
Plan tiers
See What’s included for coverage, guarantees and commercial terms.
From request to live
Every item moves through five states on the delivery board:
Tracking delivery covers the board, epics, decisions and risks.
Scopes
A scope is a pre-defined piece of delivery work with a known shape and finish state — a new feature, an old framework upgrade, a new platform, or ongoing operations under a service level. Browse them at scrums.com/ai-development/scopes. Add any scope to your plan. Your delivery team runs it from your prioritised backlog like any other request, at no additional cost — scopes are included on every tier. They are a shortcut to a well-defined brief, not a separate purchase. Scopes are a starting point, not a limit. Work that does not match one is scoped from scratch against the same plan.Next
- What’s included — coverage, guarantees, commercials
- Starting your plan — day 0 to first deliverable
- Making requests — how to write a request the team can scope
- Tracking delivery — the board, epics, decisions and risks