# Coordinate AI development across teams

Taiga Learning · Worksheet
https://taiga.training/en/lessons/development-at-scale/

Use fictional or approved information. Do not put secrets in this worksheet.

## Learning objectives
- Identify constraints that code generation does not remove.
- Define a shared contract and its change owner.
- Distinguish local output from organization-wide delivery performance.

## Exercise
Map a fictional customer export across identity, billing, data, and platform teams. Name one shared contract and its owner. Mark each waiting point. Propose one change that reduces coordination without removing a necessary control. Define how you would observe its effect.

## Your response
- Scenario and scope:
- Assumptions and open questions:
- Proposed answer or decision, with reasons:

## Verify your response
| Claim or criterion | Evidence or test | Result or gap | Owner |
| --- | --- | --- | --- |
| | | | |
| | | | |
| | | | |

## Next action
- Action, owner, and date:
- When will you review this response?

## Principle to retain
More generated changes need a delivery system that can absorb them. Coordinate contracts, ownership, verification, and operations across teams.

## Sources
- [DORA: Loosely coupled teams](https://dora.dev/capabilities/loosely-coupled-teams/)
- [DORA: 2025 research report](https://dora.dev/research/2025/dora-report/)
- [CNCF: Platforms White Paper](https://tag-app-delivery.cncf.io/whitepapers/platforms/)

This worksheet supports learning. Completing it does not itself authorize a production change.