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 Expectation Mapping.
Facilitation
Expectation Mapping
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
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
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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.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
LowMediumMediumLow
Timedifferent
45-90 min60-120 min3–4 h for initial assessment; preparation and deeper analysis additionalHalf day initial, dann laufend
Participantsdifferent
3-122-81 or a small team; particularly suitable for 3–4 peopleEin Team plus Stakeholder
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Expectation Map, Alignment Notes, AgreementsCommunication Canvas, Stakeholder Messages, Architecture Communication PlanLean 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
AlignmentStakeholdersTeam
ArchitectureCommunicationStakeholdersCanvas
ArchitectureQualityRiskAssessmentLean
TeamAlignmentCommunicationService
Add more methods