methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of Team API with its method-specific working model.
Team Design
Team API
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration for Communication Plan
Delivery
Communication Plan
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Purposedifferent
When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost.When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.
Complexitydifferent
LowMediumLowLow
Timedifferent
Half day initial, dann laufend2–4 h review as a planning range; preparation and evaluation additional45-90 min45-90 min
Participantsdifferent
Ein Team plus StakeholderDesigners, developers as users, and facilitation2-63-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Team API DocumentPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsCommunication Plan, Channel Matrix, Message CadenceExpectation Map, Alignment Notes, Agreements
Tagsno overlap
TeamAlignmentCommunicationService
ArchitectureEngineeringFeedbackValidationTasks
CommunicationStakeholdersDeliveryPlanning
AlignmentStakeholdersTeam
Add more methods