Team Topologies on Team API

The team API includes:

• Code: runtime endpoints, libraries, clients, UI, etc. produced by the team
• Versioning: how the team communicates changes to its code and services (e.g., using semantic versioning [SemVer] as a “team promise” not to break things)
• Wiki and documentation: especially how-to guides for the software owned by the team ​
• Practices and principles: the team’s preferred ways of working ​
• Communication: the team’s approach to remote communication tools, such as chat tools and video conferencing
• Work information: what the team is working on now, what’s coming next, and overall priorities in the short to medium term ​
• Other: anything else that other teams need to use to interact with the team⊕ (Skelton and Pais 2019, chap. 3)