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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Three Amigos method illustration showing its working structure
Agile
Three Amigos
Purposedifferent
arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.When story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process.
Complexitydifferent
LowLowMediumLow
Timedifferent
1-2 Tage20-40 min pro Story3–4 h for initial assessment; preparation and deeper analysis additional15-30 min
Participantsdifferent
1-43-61 or a small team; particularly suitable for 3–4 people3
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewAcceptance Criteria, Story UpdateLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checksClarified Story, Test Examples, Open Questions
Tagsno overlap
ArchitectureDocumentationCommunication
AgileRequirementsRefinementBehavior-Driven Development
ArchitectureQualityRiskAssessmentLean
CollaborationBehavior-Driven DevelopmentQualityRefinement
Add more methods