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
Paper illustration for Standard Work Analysis.
Operations
Standard Work Analysis
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
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 the same task is done differently depending on the person, the method exposes the reliable core. It creates comparability without unnecessarily choking off needed latitude.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.
Complexitydifferent
MediumMediumHighLow
Timedifferent
30-60 min1-3 h2-6 h30-120 min
Participantsdifferent
2-62-63-102-6
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Smaller Stories, Acceptance Criteria, Split RationaleStandard Work Sheet, Deviation List, Improved Standard, Training NeedsFMEA Table, Risk Priority, Mitigation ActionsObservation Notes, Improvement Ideas
Tagsno overlap
BacklogIterationDelivery
LeanProcessQuality
RiskQualityOperationsRoot cause
LeanObservationProcessOperations
Add more methods