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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Weekly Review.
Operations
Weekly Review
Purposedifferent
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.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.ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.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
MediumMediumHighLow
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional1-2 h Setup, laufendSeveral meetings plus preparation and analysis; total effort depends on scope30-60 min
Participantsdifferent
Designers, developers as users, and facilitation1Evaluation team, architects, and relevant stakeholders1
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncAsync
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsAction Lists, Project List, Review RoutinePrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsUpdated Task System, Weekly Focus, Next Actions
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
ProductivityPlanningTasksExecution
ArchitectureQualityRiskTradeoffsStakeholders
ProductivityExecutionPlanning
Add more methods