Collaboration

Gathers ideas silently and iteratively, builds on them together, and produces prioritized concepts instead of loud individual impulses.

Core question: What different ideas emerge when everyone writes silently first and then builds on others’ contributions?

• 15-30 min
• 3-12

Moves incident response into a shared thread, connects alerts with commands, and keeps decisions traceable.

Core question: Which operational action benefits from shared visibility, and what controls prevent misuse?

• Ongoing
• 2-20

Brings business, development, and testing together before implementation to clarify a story's examples, rules, and edge cases.

Core question: Which examples express business intent, technical feasibility and testable behavior?

• 15-30 min
• 3

Brings sketches, critique, and iteration together so solid design decisions grow out of early drafts.

Core question: Which design best addresses the concrete user problem and what do alternatives teach us?

• 1-3 h
• 3-8

Clarifies purpose, roles, and working rules in a charter that makes collaboration tangible and verifiable.

Core question: What shared agreement enables this team to fulfil its mandate with clear boundaries and responsibilities?

• 2-4 h
• 3-12

Jointly formulates valid working rules and clarifies how the team handles expectations, conflicts, and reviews.

Core question: Which observable agreements help this team collaborate reliably and respectfully?

• 45-90 min
• 3-12

Moves team boundaries, interfaces, and collaboration toward a concrete result through "prepare the team list", "explain the three modes with examples", and "document agreements per pair".

Core question: Which interaction mode supports this outcome with the least persistent coupling?

• Half day
• Team-Leads plus Architecture

Parallel design teams turn a shared challenge into comparable concepts, open questions, and a consolidated direction.

Core question: Which integrated design option best satisfies the agreed criteria?

• Halber Tag bis mehrere Tage
• 10-50