View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Polarity MappingLASR (Lightweight Approach for Software Reviews)Acceptance Criteria WorkshopSpecification by Example
| Criterion |  Systems Thinking Polarity Mapping |  Architecture LASR (Lightweight Approach for Software Reviews) |  Agile Acceptance Criteria Workshop |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely. | 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 story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-2 h | 3–4 h for initial assessment; preparation and deeper analysis additional | 20-40 min pro Story | 60-90 min pro Feature |
Participantsdifferent | 3-12 | 1 or a small team; particularly suitable for 3–4 people | 3-6 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | 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 | Acceptance Criteria, Story Update | Example Table, Acceptance Tests |
Tagsno overlap | Systems thinkingTradeoffsLeadership | ArchitectureQualityRiskAssessmentLean | AgileRequirementsRefinementBehavior-Driven Development | AgileRequirementsExamplesBehavior-Driven Development |