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
Story Splitting method illustration showing its working structure
Agile
Story Splitting
Value Stream Mapping workspace showing the question, observations, and next decision.
Delivery
Value Stream Mapping
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Paper illustration of MORT Analysis with its method-specific working model.
Operations
MORT Analysis
Purposedifferent
When a story becomes too large for a clean flow, it breaks scope down along value and risk. It shapes the work into a form that ships earlier and is easier to verify.When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible.For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps.
Complexitydifferent
MediumMediumMediumHigh
Timedifferent
30-60 min1-3 h2-4 hMehrere Tage bis Wochen
Participantsdifferent
2-64-102-62-6
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Smaller Stories, Acceptance Criteria, Split RationaleCurrent-state map, Future-state map, Bottleneck listBarrier Inventory, Failure Analysis per Barrier, Action BacklogMORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations
Tagsno overlap
BacklogIterationDelivery
LeanFlowWasteDelivery
Root causeSafetyIncident
Root causeSafetySystemicIncident
Add more methods