liveBook · Manning

Team charter

As explained in Think Like a CTO

A team charter is a concise document defining a team's purpose, responsibilities, expectations, resources, and contribution to the wider organization.

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:

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

How Think Like a CTO covers it

How deep it goes
Keeps the charter concise and high-level, specifying responsibilities, resources, and success measures rather than an elaborate document.
Examples
Uses an online product support team, with defined service boundaries, customers, resources, skills, and performance measures.
What it assumes
Starts with team purpose and explains how to discover inherited responsibilities before making changes.
What you can do after
Build it from scratch by defining a team's purpose, responsibilities, customers, resources, skills, and success measures.
How it connects
Connects team purpose to organizational alignment, resource planning, knowledge capture, and success metrics.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a CTO. The section links point to the parts of the book it draws on.