---
title: "Agile Team Charter Template"
methodology: "universal"
complexity: "intermediate"
owner: "mirichard"
updated: "2026-09-19"
primary_principles: ["collaborative-leadership", "continuous-learning"]
secondary_principles: ["adaptability", "stewardship"]
principle_rationale: "Creates accountable team agreements that support adaptation, trust, and learning."
---


# Agile Team Charter Template

## When to Use

- When forming or resetting an Agile team with shared product goals.
- When team members need working agreements, decision rights, and a Definition of Done.

## When NOT to Use

- To impose a manager's task allocation in place of team planning.
- Do not represent author self-checks as independent or authorized approval. See [Self-approval](../../../../../docs/principles/anti-patterns.md#self-approval).

## Pairs Well With

- [Team Charter Template](../../../../../domains/team/project-lifecycle/02-planning/resource-planning/team-charter-template.md).
- [Sprint Planning Template](../../../../../domains/delivery/templates/agile/sprint_planning_template.md).

Selection context: Team domain; universal methodology; intermediate complexity. Match the situations above to project phase, risk, team size, and industry using the [decision-engine context model](../../../../../meta/architecture-research/800-801-context-assessment-model.md).

## Purpose/Overview
This agile team charter template establishes the foundation for effective agile teams by defining mission, values, and working agreements. It serves as a living document that guides team behavior, decision-making, and collaboration within the Scrum framework. The charter promotes team self-management and continuous improvement.

## Usage Instructions
1. **Team Workshop**: Create the charter collaboratively during a team formation workshop
2. **Living Document**: Regularly review and update based on team retrospectives
3. **Daily Reference**: Use working agreements to guide daily interactions and decisions
4. **Onboarding**: Share with new team members as part of their orientation
5. **Conflict Resolution**: Reference values and agreements when resolving team conflicts
6. **Continuous Improvement**: Update the charter based on team learning and growth
7. **Visibility**: Keep the charter visible and accessible to all team members
8. **Alignment**: Ensure the charter aligns with organizational values and project goals

## Team Information
- **Team Name**: [Team Name]
- **Product Owner**: [Name]
- **Scrum Master**: [Name]
- **Team Members**: [List team members]

## Mission Statement
[Brief statement describing the team's purpose and primary focus]

## Product Vision
[Description of the product or solution the team is building]

## Team Goals and Objectives
- [Goal 1]
- [Goal 2]
- [Goal 3]

## Team Values and Working Agreements
### Core Values
- [Value 1]
- [Value 2]
- [Value 3]

### Working Agreements
- [Agreement 1]
- [Agreement 2]
- [Agreement 3]

## Definition of Done
- [ ] [Criteria 1]
- [ ] [Criteria 2]
- [ ] [Criteria 3]

## Communication Protocols
- **Daily Standups**: [Time and location]
- **Sprint Planning**: [Frequency and duration]
- **Sprint Reviews**: [Frequency and duration]
- **Retrospectives**: [Frequency and duration]

## Roles and Responsibilities
| Role | Responsibilities |
|------|-----------------|
| Product Owner | [Responsibilities] |
| Scrum Master | [Responsibilities] |
| Developers | [Responsibilities] |

## Success Metrics
- [Metric 1]
- [Metric 2]
- [Metric 3]


*Agile team charter following Scrum framework principles*

Framework reference: [Scrum Guide, November 2020](https://scrumguides.org/scrum-guide.html).