Maximise Team autonomy

From go-ELSE
Revision as of 01:50, 24 January 2024 by Ppugliese (talk | contribs) (Created page with "__NOTOC__ == Description == In developing large products where many Teams are involved, reducing the amount of coordination needed to ensure Teams' coordination is paramount. It is, therefore, fundamental to find ways to maximise the autonomy of each Team in a Team of Teams. This can be achieved in several ways: * The creation of Teams with broader problem and Favour Teams with broader Solution Accountabili...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Description

In developing large products where many Teams are involved, reducing the amount of coordination needed to ensure Teams' coordination is paramount. It is, therefore, fundamental to find ways to maximise the autonomy of each Team in a Team of Teams.

This can be achieved in several ways:

  • The creation of Teams with broader problem and solution accountability is a crucial step in the right direction: when developing complex products, the competence of being able to work on broader parts of it means reducing the need of coordinating with other Teams
  • Agreeing on development standards that are accepted among all Teams reduces the need for ad-hoc processes that are prone to failures and difficult to improve, requiring additional coordination at the process level
  • Enabling Teams to validate their work as close as possible to when the work is being done to reduce coordination needed to integrate the contribution of each Team

Related Principles