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 illustration for ALPEN Method
Operations
ALPEN Method
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.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.
Complexitysame
LowLowLowLow
Timedifferent
10-20 min daily30 min Setup, dann laufend15-45 min1-2 Tage
Participantsdifferent
11-3 maintaining, briefing for everyone1-31-4
Formatdifferent
AsyncAsyncAsyncWorkshop + async
Outputdifferent
Daily Plan, Time Estimates, Review NotesRAID Log, Status Report SourceADR File, Decision Log, RationaleArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
PlanningTime managementProductivityOperations
RiskTrackingStakeholdersGovernance
ArchitectureRationaleDocumentationGovernance
ArchitectureDocumentationCommunication
Add more methods