Team Topology Simplified

I'll keep this short and precise. Team topologies have both changed and evolved over time and has been a little fuzzy to relate to the simple mind. I have attempted to simplify these using articles found on Scaled Agile and Atlassian with examples of the teams.

Stream-Aligned Teams - Stream-aligned teams focus on a single, impactful stream of work. It can be a single product or service, a single set of features, a single user journey, or a single user persona. The team is empowered to build and deliver customer or user value as quickly, safely, and independently as possible, without requiring hand-offs to other teams to perform parts of the work. Have full ownership of building, running, and fixing an application in production. Eg – Credit scoring system, new loan creation, loan servicing, loan repayment

Platform Team- Platform team provides internal services that the stream-aligned team can use. They create capabilities that can be used by numerous stream-aligned teams. Eg can be Identity Management, Payment processing, Account closure, New account creation

Complicated-Subsystem team - Team members from this team may have specialized knowledge in certain microservices (i.e., a?billing service), algorithms, or even artificial intelligence.?E.g., is credit scoring algorithm, loan interest calculation

Enabling Team – ?These teams focus on research and experimentation to make informed suggestions about tooling, frameworks, and ecosystem choices that affect the tool stack. Stream aligned team should not be dependent on the enabling team for an extended or long time or else it beats the purpose. E.g. Cloud technology enabling team, Automated testing enabling team, DevOps.?