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 Mad Sad Glad
Agile
Mad Sad Glad
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 Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Purposedifferent
When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.
Complexitydifferent
LowMediumHighLow
Timedifferent
30-60 min3–4 h for initial assessment; preparation and deeper analysis additional2-6 h30-60 min
Participantsdifferent
3-101 or a small team; particularly suitable for 3–4 people3-103-12
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Emotion Board, Themes, Action ItemsLean 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 checksFMEA Table, Risk Priority, Mitigation ActionsStart Stop Continue Board, Improvement Actions
Tagsno overlap
RetrospectiveTeamReflection
ArchitectureQualityRiskAssessmentLean
RiskQualityOperationsRoot cause
RetrospectiveImprovementTeamReflection
Add more methods