Team topology - Revision history

Root at 16:27, 22 October 2025

2025-10-22T16:27:48Z

← Older revision		Revision as of 17:27, 22 October 2025
Line 3:		Line 3:
	Derived from the groundbreaking work of Matthew Skelton and Manuel Pais, team topologies represent distinct patterns of team organization and collaboration. They recognize four fundamental team types:		Derived from the groundbreaking work of Matthew Skelton and Manuel Pais, team topologies represent distinct patterns of team organization and collaboration. They recognize four fundamental team types:

	~~<span id~~=~~"examples-~~of~~-team-~~topologies-in-action~~"></span>~~		= Examples of Team topologies in action =
	~~= Examples of Team Topologies in Action~~ =

	* '''Stream-aligned teams~~''':~~ Suppose a company has a digital platform that offers different services like e-commerce, content publishing, and user forums. Each of these can be managed by a stream-aligned team that focuses entirely on optimizing and improving that specific flow. For instance, the e-commerce team will manage everything from product listing to payment processing, ensuring that the user shopping experience is seamless.		== Stream-aligned teams ==
	* '''Platform teams''': Consider a large enterprise developing various software products. A platform team might provide a shared set of services, like a logging framework or authentication service, that all the other product teams can use. Instead of each product team developing their own authentication method, they can leverage the platform team's solution, ensuring consistency and freeing them to focus on product-specific features.		Suppose a company has a digital platform that offers different services like e-commerce, content publishing, and user forums. Each of these can be managed by a stream-aligned team that focuses entirely on optimizing and improving that specific flow. For instance, the e-commerce team will manage everything from product listing to payment processing, ensuring that the user shopping experience is seamless.
	* '''Enabling teams''': Imagine a scenario where an organization wants to adopt a new technology, such as Kubernetes for container orchestration. The existing teams might not have the expertise to use this technology efficiently. An enabling team, proficient in Kubernetes, could be formed to train, guide, and assist the other teams in adopting this new technology, ensuring a smoother transition.
	* '''Complicated subsystem teams''': In industries like aerospace or automotive manufacturing, there are often subsystems like engine control units that require deep specialization. Such subsystems are best handled by teams that focus solely on that complexity, abstracting away the intricate details from teams that focus on broader product goals.

	~~<span id~~=~~"the-so-called-spotify-model"></span>~~		== Platform teams ==
	=~~= The so called Spotify model~~ ==		Consider a large enterprise developing various software products. A platform team might provide a shared set of services, like a logging framework or authentication service, that all the other product teams can use. Instead of each product team developing their own authentication method, they can leverage the platform team's solution, ensuring consistency and freeing them to focus on product-specific features.

			== Enabling teams ==
			Imagine a scenario where an organization wants to adopt a new technology, such as Kubernetes for container orchestration. The existing teams might not have the expertise to use this technology efficiently. An enabling team, proficient in Kubernetes, could be formed to train, guide, and assist the other teams in adopting this new technology, ensuring a smoother transition.

			== Complicated subsystem teams ==
			In industries like aerospace or automotive manufacturing, there are often subsystems like engine control units that require deep specialization. Such subsystems are best handled by teams that focus solely on that complexity, abstracting away the intricate details from teams that focus on broader product goals.

			= The so called Spotify model =
	Even its one of the most referenced models, from [https://www.jeremiahlee.com/posts/failed-squad-goals/ <u>Spotify itself</u>] they say that they do not use that model anymore. Here is a briefe description of this team topology:		Even its one of the most referenced models, from [https://www.jeremiahlee.com/posts/failed-squad-goals/ <u>Spotify itself</u>] they say that they do not use that model anymore. Here is a briefe description of this team topology:

Line 23:		Line 27:
	[[File:UserDocumentation_Knowledge_Central_KC_Executive_teams_management_Team_topologyimage-20250419-095526.png\|632px\|center]]		[[File:UserDocumentation_Knowledge_Central_KC_Executive_teams_management_Team_topologyimage-20250419-095526.png\|632px\|center]]

	~~<span id="benefits-of-applying-team-topologies"></span>~~
	= Benefits of Applying Team Topologies =		= Benefits of Applying Team Topologies =

	* '''Enhanced Collaboration''': By defining clear areas of responsibility and providing teams with the autonomy to manage their domains, collaboration becomes more straightforward. Teams can work with minimal dependencies and more clear-cut interfaces with other teams.		* '''Enhanced Collaboration''': By defining clear areas of responsibility and providing teams with the autonomy to manage their domains, collaboration becomes more straightforward. Teams can work with minimal dependencies and more clear-cut interfaces with other teams.
	* '''Faster Feedback Loops''': With stream-aligned teams, feedback is direct and quick since they are closely aligned with a specific user or business function. Rapid feedback enables faster iterations and improvements.		* '''Faster Feedback Loops''': With stream-aligned teams, feedback is direct and quick since they are closely aligned with a specific user or business function. Rapid feedback enables faster iterations and improvements.
	* '''Reduced Complexity''': By dividing teams based on functionalities and expertise, complexity is localized. This reduces the overhead of coordination and simplifies decision-making.		* '''Reduced Complexity''': By dividing teams based on functionalities and expertise, complexity is localized. This reduces the overhead of coordination and simplifies decision-making.
	* '''Scalability''': As organizations grow, team topologies provide a framework to scale teams in a structured manner, ensuring that each new team has a clear purpose and domain of responsibility.		* '''Scalability''': As organizations grow, team topologies provide a framework to scale teams in a structured manner, ensuring that each new team has a clear purpose and domain of responsibility.
	~~<!-- From bodyContent 1542970.mraw -->~~

	[[Category:teams management]]		[[Category:teams management]]

Maintenance script: Added category teams management

2025-10-19T17:50:36Z

Added category teams management

← Older revision		Revision as of 18:50, 19 October 2025
Line 32:		Line 32:
	<!-- From bodyContent 1542970.mraw -->		<!-- From bodyContent 1542970.mraw -->

			[[Category:teams management]]

Maintenance script: Maintenance script moved page UserDocumentation:Knowledge Central/KC Executive/teams management/Team topology to Team topology: Cleaned title and categorized

2025-10-19T17:50:36Z

Maintenance script moved page UserDocumentation:Knowledge Central/KC Executive/teams management/Team topology to Team topology: Cleaned title and categorized

← Older revision	Revision as of 18:50, 19 October 2025
(No difference)

imported>Unknown user at 09:55, 19 April 2025

2025-04-19T09:55:32Z

@@ Line 1: / Line 1: @@
-{{AttachmentsSectionStart}}
+Derived from the groundbreaking work of Matthew Skelton and Manuel Pais, team topologies represent distinct patterns of team organization and collaboration. They recognize four fundamental team types:
-{{AttachmentsSectionEnd}}
+<span id="examples-of-team-topologies-in-action"></span>
   <!-- From bodyContent 1542970.mraw -->

imported>Unknown user at 09:55, 19 April 2025

2025-04-19T09:55:32Z

← Older revision	Revision as of 10:55, 19 April 2025
(No difference)

imported>Unknown user at 09:55, 19 April 2025

2025-04-19T09:55:32Z

New page

{{AttachmentsSectionStart}}
* [[Media:UserDocumentation_Knowledge_Central_KC_Executive_teams_management_Team_topologyimage-20250419-095526.png]]
* [[Media:UserDocumentation_Knowledge_Central_KC_Executive_teams_management_Team_topologyimage-20250419-095526.png]]

{{AttachmentsSectionEnd}}