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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Paper illustration for ALPEN Method
Operations
ALPEN Method
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.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time.
Complexitydifferent
MediumMediumLowLow
Timedifferent
6 Wochen Cycle + 2 Wochen Cool-DownAs needed20-45 min10-20 min daily
Participantsdifferent
2-4 pro Pitch4-153-121
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Pitches, Bet-table decisions, Hill charts, Cooldown outcomesIncident Log, Action Tracker, Stakeholder UpdatesLessons learned, Action items, Event summaryDaily Plan, Time Estimates, Review Notes
Tagsno overlap
PlanningDeliveryAutonomy
IncidentOperationsReliability
LearningOperationsImprovement
PlanningTime managementProductivityOperations
Add more methods