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 tomato timer connects a focus task, short breaks and a work record.
Operations
Pomodoro Technique
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)
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
For easily distracted solo work, the method sets clear time boundaries for concentrated work. It protects attention when large tasks would otherwise fall apart into small avoidance moves.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.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
LowMediumMedium
Timedifferent
25 min Zyklen3–4 h for initial assessment; preparation and deeper analysis additional2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
11 or a small team; particularly suitable for 3–4 peopleDesigners, developers as users, and facilitation
Formatdifferent
AsyncWorkshop + asyncWorkshop + async
Outputdifferent
Focus Sessions, Task Progress, Interruption NotesLean 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 checksPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
FocusTime managementProductivityExecution
ArchitectureQualityRiskAssessmentLean
ArchitectureEngineeringFeedbackValidationTasks
Add more methods

Often compared together

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

Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Eat the Frog
Operations
Eat the Frog
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Paper illustration for Risk Storming.
Architecture
Risk Storming