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-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration for Expectation Mapping.
Facilitation
Expectation 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 Team API with its method-specific working model.
Team Design
Team API
Purposedifferent
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.When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.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 expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document.
Complexitydifferent
LowLowMediumLow
Timedifferent
1-2 Tage45-90 min3–4 h for initial assessment; preparation and deeper analysis additionalHalf day initial, dann laufend
Participantsdifferent
1-43-121 or a small team; particularly suitable for 3–4 peopleEin Team plus Stakeholder
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewExpectation Map, Alignment Notes, AgreementsLean 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 checksTeam API Document
Tagsno overlap
ArchitectureDocumentationCommunication
AlignmentStakeholdersTeam
ArchitectureQualityRiskAssessmentLean
TeamAlignmentCommunicationService
Add more methods