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 WorkshopCompetency QuestionsLASR (Lightweight Approach for Software Reviews)Linked Open Terms
| Criterion |  Agile Acceptance Criteria Workshop |  Knowledge Modeling Competency Questions |  Architecture LASR (Lightweight Approach for Software Reviews) |  Knowledge Modeling Linked Open Terms |
|---|---|---|---|---|
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. | Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures. | 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. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 20-40 min pro Story | 2-4 h | 3–4 h for initial assessment; preparation and deeper analysis additional | Wochen bis Monate |
Participantsdifferent | 3-6 | 2-8 | 1 or a small team; particularly suitable for 3–4 people | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Acceptance Criteria, Story Update | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | 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 | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan |
Tagsno overlap | AgileRequirementsRefinementBehavior-Driven Development | OntologyKnowledge graphScopeRequirementsSemantic | ArchitectureQualityRiskAssessmentLean | OntologyMethodologyAgileSemantic |