Autonomy

As explained in Collaborative Software Design: How to facilitate domain modeling decisions

Autonomy is the ability of a team to make decisions and progress independently without requiring continual alignment or approval from other teams.

Autonomy is a team’s ability to make decisions and move work forward independently, without continual alignment or approval from other teams. It matters because shared decisions can interrupt development flow even when teams own distinct bounded contexts. section 10.3.1

Four teams around a shared model

Four teams own separate bounded contexts within a large monolithic application, but those contexts depend on a shared kernel. Changing the shared model requires consultation, synchronization, and potentially changes in every team’s code or database design, reducing autonomy. section 10.3.1

Figure 10.8 A shared kernel pattern. Four teams each own their own bounded context, but they share a model. Every time that model is affected, they need to talk to the other teams to change it.

Use the shared-kernel diagram to see how one shared model creates dependencies among otherwise separately owned bounded contexts. section 10.3.1

How Collaborative Software Design: How to facilitate domain modeling decisions covers it

How deep it goes

Defines autonomy through a shared-kernel scenario and shows how synchronization reduces it, without detailing alternative architectures.

Examples

Uses four teams, a monolithic application, separately owned bounded contexts, and a shared model as the concrete example.

What it assumes

Assumes familiarity with teams and software systems while introducing bounded contexts and shared kernels through the scenario.

What you can do after

Evaluate how shared models and required coordination constrain independent team progress.

How it connects

Connects autonomy to microservices architecture, monolithic architecture, bounded contexts, shared kernel, and Domain-Driven Design.

liveBookmanning.com

Read Collaborative Software Design: How to facilitate domain modeling decisions on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Effective Platform EngineeringAutonomy is the ability of developers or teams to work and make decisions independently within their responsibilities.
• 

  liveBookmanning.com
  AI Agents in Action, Second EditionAutonomy is the capacity of a system to select and perform actions without requiring a separate user decision for each step.
• 

  liveBookmanning.com
  Architecture Modernization: Socio-technical alignment of software, strategy, and structureThe ability of a product, team, or organizational unit to make decisions and operate independently.
• 

  liveBookmanning.com
  Think Like a Software Engineering ManagerAutonomy is the capacity of an individual or team to make decisions and act without continuous direction from a leader.
• 

  liveBookmanning.com
  Build an AI Agent (From Scratch)Autonomy is the capacity of a system to determine and continue its own actions without a predetermined sequence controlling every step.
• 

  liveBookmanning.com
  Lead Developer Career GuideThe ability and authority to act, make decisions, and solve problems independently.
• 

  liveBookmanning.com
  Software Testing with Generative AIThe capacity of a software system to select and perform actions toward a goal without an explicitly ordered sequence being prescribed for every action.
• 

  liveBookmanning.com
  Think Like a CTOAutonomy is the authority of a person or team to make decisions and handle work independently within defined boundaries.

Compare how 9 books explain autonomy →

Related concepts

• microservice architectureproduced by · Microservice architecture is a software architectural style that organizes an application as independently deployable services with focused responsibilities that communicate through defined interfaces.
• intrinsic motivationpart of · Intrinsic motivation is motivation arising from interest, enjoyment, satisfaction, or challenge inherent in an activity rather than from external rewards or pressures.
• human-in-the-loopcontrasts with · Human-in-the-loop is a system pattern in which people provide input, judgment, review, or intervention within an automated process.
• stream-aligned teamused by · A stream-aligned team is a long-lived team organized around a continuous flow of customer or business value, with responsibility for delivering and maintaining its product or service.

This explainer was generated by Manning's knowledge graph from the text of Collaborative Software Design: How to facilitate domain modeling decisions. The section links point to the parts of the book it draws on.