View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Feynman Technique |  UX Research HEART Framework |  Agile Sprint Retrospective |  Engineering Goal Question Metric |
|---|---|---|---|---|
Purposedifferent | The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work. | Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard. | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 20-60 min | 120 min initial, dann laufend | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 90-180 min |
Participantsdifferent | 1 | 3-6 | Scrum Team | 3-6 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | Plain-language Explanation, Knowledge Gaps, Study Notes | HEART-GSM Table, Dashboard | Improvement actions, Team agreements | GQM Table, Metric Profiles |
Tagsno overlap | LearningKnowledgeUnderstanding | MetricsUX researchMeasurementSatisfaction | RetrospectiveImprovementLearning | MetricsMeasurementEngineeringAlignment |