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 Affinity Estimation |  Delivery Value Stream Mapping |  Agile Planning Poker |  Engineering Kanban |
|---|---|---|---|---|
Purposedifferent | When many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes. | When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 30-90 min | 1-3 h | 2-5 min je Item | Ongoing |
Participantsdifferent | 3-12 | 4-10 | 3-9 | 2-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Affinity Size Map, Grouped Estimates, Unclear Items | Current-state map, Future-state map, Bottleneck list | Relative Estimates, Assumption Notes, Split Candidates | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | EstimationBacklogRelative sizing | LeanFlowWasteDelivery | EstimationAgileRelative sizingTeam | FlowVisual managementDelivery |