CHAPTER 42Team Types
SVPG has had the opportunity to observe and advise on the team topology of hundreds of tech companies.
While every situation truly is unique when it comes to topology, there are some important best practices that can help you optimize your topology for empowerment.
In this chapter we consider the two fundamental types of product teams: platform teams, which manage services so they can be easily leveraged by other teams, and experience teams, which are responsible for how the product value is exposed to users and customers.
It's important to emphasize that any topology must consider both the underlying technology architecture as well as the broader strategic context (including the business objectives, product vision, strategy, etc.) of the product.
This means that it's essential that product and engineering leadership must determine the topology together.
Platform Teams
Platform teams provide leverage because they allow for common services to be implemented once but used in many places. Examples of this include:
- A platform team that is responsible for shared services such as authentication or authorization
- A platform team that is responsible for maintaining a library of reusable interface components
- A platform team that is responsible for providing tools to developers for test and release automation
Platform teams also allow for managing complexity because they can encapsulate particularly difficult or specialized areas of the product. Examples of this ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access