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 for NoEstimates.
Agile
NoEstimates
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for Causal Factor Analysis.
Operations
Causal Factor Analysis
Paper illustration for Current Reality Tree
Systems Thinking
Current Reality Tree
Purposedifferent
When estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules.After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.For an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events.A Current Reality Tree condenses many symptoms into a few causal chains. The method makes visible which core problems drive several negative effects at once.
Complexitydifferent
MediumMediumHighHigh
Timedifferent
laufend30-90 min2-6 h2-6 h
Participantsdifferent
2-123-123-103-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Throughput Data, Flow Forecast, Slicing RulesPostmortem Doc, Action Items, TimelineEvent Timeline, Causal Factor Chart, Cause List, Corrective ActionsCurrent Reality Tree, Core Problems, Intervention Ideas
Tagsno overlap
EstimationForecastingFlow
Site Reliability EngineeringIncidentLearningReliability
CausalityIncidentRoot causeTimeline
Systems thinkingRoot causeConstraintsCausality
Add more methods