View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Specification by Example |  Agile Example Mapping |  DevOps Incident Timeline Analysis |  Operations Causal Factor Analysis |
|---|---|---|---|---|
Purposedifferent | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | For an incident with an unclear sequence, the method makes the timeline precisely visible. It separates perception, reaction, and delay so cause and effect become more clearly readable. | 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. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 60-90 min pro Feature | 30-60 min | 60-180 min | 2-6 h |
Participantsdifferent | 3-6 | 3-7 | 3-10 | 3-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions | Incident Timeline, Evidence Log, Delay Analysis, Improvement Actions | Event Timeline, Causal Factor Chart, Cause List, Corrective Actions |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement | IncidentTimelineSite Reliability Engineering | CausalityIncidentRoot causeTimeline |