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

# Dedicated Teams

> Add a complete engineering team with explicit roles, ownership, governance, and delivery expectations.

## When to use a dedicated team

A dedicated team gives you a stable, cross-functional delivery unit for an ongoing roadmap. Use this model when the constraint is a whole team rather than one specialist or one bounded scope.

## Define the team

Agree:

* Required roles and seniority
* Product and technical ownership
* Day-to-day management responsibilities
* Backlog and prioritization process
* Quality, security, and release controls
* Reporting and escalation cadence
* Scaling and replacement procedures

<Note>
  Do not infer management ownership from the team label alone. Record whether you, Scrums.com, or both parties manage day-to-day delivery in the service-line agreement.
</Note>

## Onboard the team

Provide product context, architecture, repositories, environments, working agreements, and initial priorities. Start with a small, accepted delivery milestone before expanding access or scope.

[Explore dedicated teams →](https://www.scrums.com/hire/teams)