The API product teams are accountable and responsible for individual API products, and are therefore also responsible for executing all of the activities of the API life cycle (refer to Chapter 7, API Life Cycle, for more details on the API life cycle).
There can be as many API product teams as required, as long as there is a clear understanding of which team owns which API. Ideally, there should be one-to-one mapping (one product to one team); however, on occasion, it might make sense to give a team more than one API. This should be done with caution in order to avoid the team becoming too stretched to the point that features are no longer delivered frequently.
Furthermore, it is recommended that API product teams should ...
