Create advanced Works with: Any AI

Scaling Agile: Coordination Between Teams

Table output Has example

Reduce friction among several teams.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

Design coordination for several agile teams. Teams and their areas: [TEAMS_AREAS]. Shared components and dependencies: [DEPENDENCIES]. Current pain points: [PAIN_POINTS].

Propose lightweight coordination mechanisms: a cross-team planning event, a dependency board, a scrum of scrums, shared definition of done, and an architecture sync. For each describe purpose, participants, cadence, inputs and outputs. Compare with heavier frameworks in a table without recommending any, listing the conditions where each fits. Provide a six-week experiment plan with measures and a check on the overhead created. Include a risk list for coordination, such as meeting overload.

Add a section on measuring the overhead of coordination, such as hours per person per week, and a stop rule if overhead exceeds a threshold I set. Provide a one-page working agreement between teams about interfaces, release timing, and who decides when there is a conflict, and a way to run the experiment retrospective.

Also name the single mechanism you would start with if only one could be tried, and the evidence that would show it is working.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Teams: Mobile, Web, Platform. Dependencies: Platform releases an API each month.
Mechanisms
Cross-team planning event: every 8 weeks, 3 hours, product owners and tech leads, output: dependency board.
Dependency board: weekly 15 minutes, tickets with owner and date.
Scrum of scrums: twice a week, 15 minutes.
Experiment (6 weeks): measure hours of coordination per person per week; target under 2.
Heavier frameworks table: not recommended without conditions.
Risks: meeting overload; mitigation: stop rule if overhead goes above 3 hours.
Review after six weeks: keep what saved time, drop what only produced notes, and record the decision.

• agile