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 Story Splitting |  Agile Planning Poker |  Product Discovery Product Kata |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | When a story becomes too large for a clean flow, it breaks scope down along value and risk. It shapes the work into a form that ships earlier and is easier to verify. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. | Product Kata helps clarify customer problems, solution ideas, and evidence through a repeatable improvement routine. It captures direction, current metric, target metric, experiment notes, and learning. | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 30-60 min | 2-5 min je Item | 1-2 Wochen je Loop | 45–75 min |
Participantsdifferent | 2-6 | 3-9 | 3-10 | Team members involved |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Smaller Stories, Acceptance Criteria, Split Rationale | Relative Estimates, Assumption Notes, Split Candidates | Direction, Current metric, Target metric, Experiment note, Learning report | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | BacklogIterationDelivery | EstimationAgileRelative sizingTeam | OutcomesDiscoveryLearningIterationCoaching | RetrospectiveLearningReflectionTeam |