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 Shape Up with its method-specific working model.
Delivery
Shape Up
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration for Hypothesis-Driven Troubleshooting.
Engineering
Hypothesis-Driven Troubleshooting
Paper illustration for Communication Plan
Delivery
Communication Plan
Purposedifferent
Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts.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 systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable.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.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
6 Wochen Cycle + 2 Wochen Cool-Down2–4 h review as a planning range; preparation and evaluation additional30-240 min45-90 min
Participantsdifferent
2-4 pro PitchDesigners, developers as users, and facilitation1-62-6
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Pitches, Bet-table decisions, Hill charts, Cooldown outcomesPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsHypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryCommunication Plan, Channel Matrix, Message Cadence
Tagsno overlap
PlanningDeliveryAutonomy
ArchitectureEngineeringFeedbackValidationTasks
TroubleshootingProblem solvingDiagnosis
CommunicationStakeholdersDeliveryPlanning
Add more methods