View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Example MappingLASR (Lightweight Approach for Software Reviews)Architecture Communication Canvas
| Criterion |  Agile Example Mapping |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture Architecture Communication Canvas |
|---|---|---|---|
Purposedifferent | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 30-60 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 60-120 min |
Participantsdifferent | 3-7 | 1 or a small team; particularly suitable for 3–4 people | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Lean 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 checks | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ArchitectureQualityRiskAssessmentLean | ArchitectureCommunicationStakeholdersCanvas |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
