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 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
Paper illustration for Risk Storming.
Architecture
Risk Storming
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update.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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.
Complexitydifferent
LowLowLowMedium
Timedifferent
20-40 min pro Story30-60 min60-90 min2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
3-63-74-12Designers, developers as users, and facilitation
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Acceptance Criteria, Story UpdateExample Map, Acceptance Criteria, Open QuestionsAnnotated Diagram, Prioritized Risk List, Action BacklogPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
AgileRequirementsRefinementBehavior-Driven Development
Behavior-Driven DevelopmentRequirementsExamplesRefinement
RiskArchitectureWorkshopValidation
ArchitectureEngineeringFeedbackValidationTasks
Add more methods