A team charter concisely states why a team exists, what it is responsible for, and how it contributes to the wider organization. Make it available to the group, identify the resources needed, and give the team leader support and room to execute. section 6.1 section 6.8
A practical charter can specify:
- Purpose and contribution to organizational success. section 6.1
- Responsibilities, including what the team does not own. section 6.1.2
- Customers, resources, and required skills. section 6.1.2
- Measures of success. section 6.9
Online product support team
A support team might help users with the online experience and onboarding, handle data changes, and file bug or feature tickets without making code changes. Its charter can name its customers, required access and skills, and measures such as time to close requests. section 6.1.2
When taking over an established team, first learn what it does and why before changing its charter. Document team knowledge and processes so new members can contribute and the group does not depend on one person. section 6.1 section 6.1.1
