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
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 Sailboat Retrospective
Agile
Sailboat Retrospective
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective
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.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 a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued.
Complexitydifferent
LowMediumLowLow
Timedifferent
45-90 min3–4 h for initial assessment; preparation and deeper analysis additional45-90 min45-90 min
Participantsdifferent
3-121 or a small team; particularly suitable for 3–4 people4-124-12
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Expectation 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 checksSailboat Board, Risks, Improvement ActionsStarfish Board, Practice Changes, Experiments
Tagsno overlap
AlignmentStakeholdersTeam
ArchitectureQualityRiskAssessmentLean
RetrospectiveTeamImprovement
RetrospectiveImprovementExperimentsTeam
Add more methods