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
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
Paper illustration of Specification by Example with a method-specific labelled workspace.
Agile
Specification by Example
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Purposedifferent
For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together.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.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.
Complexitysame
MediumMediumMedium
Timedifferent
Ongoing60-90 min pro FeatureAs needed
Participantsdifferent
2-203-64-15
Formatdifferent
Workshop + asyncWorkshopWorkshop + async
Outputdifferent
Chat Transcript, Action Log, AutomationsExample Table, Acceptance TestsIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
CollaborationEngineeringIncident
AgileRequirementsExamplesBehavior-Driven Development
IncidentOperationsReliability
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
Paper illustration of a yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem