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 radar with five axes, two current and target profiles, and evidence cards beside each dimension.
Decision Making
Radar
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
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)
Paper illustration of Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
Purposedifferent
When capabilities, maturity levels, or market positions need to be compared across several dimensions, overview is easily lost. Radar brings different characteristics into a shared picture and shows patterns faster than tables do.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.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 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.
Complexitydifferent
MediumLowMediumLow
Timedifferent
1-2 h30-60 min3–4 h for initial assessment; preparation and deeper analysis additional20-40 min pro Story
Participantsdifferent
2-103-71 or a small team; particularly suitable for 3–4 people3-6
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Radar Map, Capability Scores, Action AreasExample Map, Acceptance Criteria, Open QuestionsLean 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 checksAcceptance Criteria, Story Update
Tagsno overlap
AssessmentPortfolioCapability
Behavior-Driven DevelopmentRequirementsExamplesRefinement
ArchitectureQualityRiskAssessmentLean
AgileRequirementsRefinementBehavior-Driven Development
Add more methods