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

# FAQs

> Answers to the most commonly asked questions about Scrums.com, SEOP, and the delivery models.

## Getting started

**How quickly can Scrums.com get started?** Most engagements begin within 21 days of contract signing. Outcome Driven Sprints can kick off within one month. Emergency deployments for critical projects can sometimes be accelerated — speak to your Enablement Partner.

**Do I need to have an existing engineering team?** No. PDaaS and Dedicated Teams are designed for organisations without an existing delivery team. Staff Augmentation requires a team for engineers to integrate into.

**What if I'm not sure which delivery model I need?** Start with an Outcome Driven Sprint. A DevOps Health Check, Engineering Discovery, or Architecture Sprint will give you a clear picture of where to invest. Your Enablement Partner will guide you from there.

***

## Pricing & billing

**How does billing work for Talent Seats?** Seats are billed at a fixed monthly rate for up to 160 hours of capacity. The rate does not vary based on exact utilisation within that allocation.

**What is the management fee?** For usage-based products (cloud infrastructure, API usage) and hourly talent, Scrums.com adds a management fee to the base cost. This covers delivery governance, platform access, operational oversight, and management support.

**Can I cancel my subscription?** Subscriptions require a minimum 12-month commitment. After the initial term, monthly rolling renewal applies. Please refer to your MSA for full cancellation terms.

**When are invoices issued?** All projects are invoiced on the 1st of every month. Your first invoice is issued within 24 hours of contract signing; ongoing invoices follow the monthly cycle from then on.

**How does billing work for hourly engagements?** You are invoiced for actual hours delivered each month. At the end of each quarter, Scrums.com runs a reconciliation: unused billed hours are credited to your account and any hours worked but not yet billed are invoiced. Detailed timesheets are provided at quarter-end.

**Where do I find my invoices?** Invoices are available in **Settings > Billing > Invoice History**. You can download PDFs from there. For billing queries, contact [billing@scrums.com](mailto:billing@scrums.com).

For full billing terms, see [Billing & Usage](/docs/administration/billing).

***

## Teams & talent

**Can I choose which engineers are on my team?** For Staff Augmentation, you select from a curated shortlist. For Dedicated Teams, Scrums.com assembles the team on your behalf based on your requirements — you do not select individuals.

**What happens if an engineer is not performing?** Raise the concern with your Enablement Partner. Scrums.com guarantees a free replacement, typically completed within 15–20 business days.

**Do engineers work exclusively on my project?** Yes. All Scrums.com Talent Seats and Dedicated Teams are exclusively dedicated to your engagement for the contracted hours.

**How long does it take to onboard a new engineer?** Engineers are typically ready to start within 21 days of your request being confirmed, or less depending on the availability of the resource you've selected.

***

## Platform & security

**Who owns the code written by Scrums.com engineers?** You do. All IP created during an engagement is assigned to the client upon delivery, subject to payment obligations. See [IP Ownership](/docs/security/ip-ownership) for full details.

**Is my data safe on the Scrums.com platform?** Yes. Data is encrypted in transit (TLS 1.2+) and at rest (AES-256). Access is governed by RBAC. Enterprise clients can access audit logs and configure SSO/SAML. See [Data Protection & Privacy](/docs/security/data-protection) for full details.

**Can AI agents access my production systems?** AI Agents operate within defined governance boundaries and cannot access systems outside their configured scope or take autonomous action without logging. See [AI Usage Boundaries & Controls](/docs/products/agents/ai-controls).

***

## More resources

For a broader set of FAQs, visit [scrums.com/faqs](https://www.scrums.com/faqs) or visit the specific product pages:

* [Talent Augmentation](https://www.scrums.com/products/augmented)
* [Team Augmentation](https://www.scrums.com/products/dedicated)
* [Managed Services](https://www.scrums.com/products/product-development-as-a-service)
* [Outcome Driven Sprints](https://www.scrums.com/products/on-demand)