Scribd
Upload
715 views

Getting Started With Team Topologies - v1

The document provides guidance on applying team topologies concepts by identifying current team types, fitting technology teams to fundamental types, and limiting cognitive load. It recommends breaking apart monoliths, using platforms to constrain solutions, identifying interaction modes, guiding collaboration, evolving structures over time, and using interactions for organizational sensing. The overall goal is to organize teams for fast workflow while producing sustainable architectures.

Uploaded by

v.karthik9993
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
715 views

Getting Started With Team Topologies - v1

The document provides guidance on applying team topologies concepts by identifying current team types, fitting technology teams to fundamental types, and limiting cognitive load. It recommends breaking apart monoliths, using platforms to constrain solutions, identifying interaction modes, guiding collaboration, evolving structures over time, and using interactions for organizational sensing. The overall goal is to organize teams for fast workflow while producing sustainable architectures.

Uploaded by

v.karthik9993
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Getting started with Team Topologies

A suggested approach to applying the concepts

1. Identify what kind of teams you currently have

Map your teams to Identify which team


common industry types to avoid or
team types change

2. Fit technology teams to the fundamental team types

Stream-aligned

Enabling

Complicated subsystem

Platform

shapes.teamtopologies.com

3. Limit the cognitive load for each team using...

Keep the team Align the team to one


stable (or engender or more areas on an
a high trust culture) ongoing basis

Break apart Provide an Limit the size of the


monoliths using underlying platform subsystem the team
natural fracture for the team to build works on
planes upon

4. Use the "Reverse Conway" approach to help to:

Drive software Produce software


systems that align to systems architectures
flow of business that are sustainable
change pressure by the organization

Constrain (and align)


the search space for
technical solutions

5. Identify as-is and to-be team interaction modes

Collaboration

X-as-a-Service

Facilitating

shapes.teamtopologies.com

6. Explicitly guide (and limit) inter-team collaboration to

Inform and guide the Drive rapid discovery and


development of internal learning at points of
Platforms and Complicated technological, organizational,
Subsystem components or situational learning

7. Evolve team structures explicitly over time

Adopt new Improve ways Avoid certain


technology of working architectures

8. Use team interactions for organizational sensing

Use front-line IT support as a Use Cybernetic control


high-skill activity that provides principles to course-correct
rapid course correction early and often

Organizing business and technology teams for fast flow


Discover more at teamtopologies.com
Find us online: @teamtopologies
v1 - 2021-04-14

You might also like