View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Acceptance Criteria WorkshopRAID LogLASR (Lightweight Approach for Software Reviews)Specification by Example
| Criterion |  Agile Acceptance Criteria Workshop |  Delivery RAID Log |  Architecture LASR (Lightweight Approach for Software Reviews) |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 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 | Low | Low | Medium | Medium |
Timedifferent | 20-40 min pro Story | 30 min Setup, dann laufend | 3–4 h for initial assessment; preparation and deeper analysis additional | 60-90 min pro Feature |
Participantsdifferent | 3-6 | 1-3 maintaining, briefing for everyone | 1 or a small team; particularly suitable for 3–4 people | 3-6 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Acceptance Criteria, Story Update | RAID Log, Status Report Source | 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 | Example Table, Acceptance Tests |
Tagsno overlap | AgileRequirementsRefinementBehavior-Driven Development | RiskTrackingStakeholdersGovernance | ArchitectureQualityRiskAssessmentLean | AgileRequirementsExamplesBehavior-Driven Development |