View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Scrum |  Knowledge Modeling Ontology Design Patterns |  Knowledge Modeling Property Graph Schema Design |  Knowledge Modeling Shape-First Modeling |
|---|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles. | Property Graph Schema Design turns business and technical requirements into a robust graph schema. It fits when query patterns, constraints, and migrations need to be thought about together. | Shape-First Modeling defines data quality through shapes before implementation or integration frays at the edges. The approach fits when validation and data contracts should be part of the design from the start. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 1-3 h pro Pattern | 4-8 h initial, dann iterativ | Halber Tag pro Domain Slice |
Participantsdifferent | 3-10 (Scrum Team) | 1-6 | 1-6 | 1-4 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Selected Patterns, Adapted Schema Fragments, Pattern Documentation | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation |
Tagsno overlap | AgileIterationCadence | OntologyPatternsReuseSemanticModeling | Knowledge graphModelingSemantic | Knowledge graphValidationSemantic |