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 notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
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 for Weekly Review.
Operations
Weekly Review
Purposedifferent
With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory.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.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.In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
1-2 h Setup, laufend2–4 h review as a planning range; preparation and evaluation additional3–4 h for initial assessment; preparation and deeper analysis additional30-60 min
Participantsdifferent
1Designers, developers as users, and facilitation1 or a small team; particularly suitable for 3–4 people1
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Action Lists, Project List, Review RoutinePrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsLean 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 checksUpdated Task System, Weekly Focus, Next Actions
Tagsno overlap
ProductivityPlanningTasksExecution
ArchitectureEngineeringFeedbackValidationTasks
ArchitectureQualityRiskAssessmentLean
ProductivityExecutionPlanning
Add more methods