View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Delivery RAID Log |  Facilitation Power Interest Grid |  Agile ROAM Board |
|---|---|---|---|---|
Purposedifferent | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | When many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy. | When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | Ongoing | 30 min Setup, dann laufend | 30-60 min | 20-40 min initial, dann laufend |
Participantsdifferent | 2-12 | 1-3 maintaining, briefing for everyone | 2-8 | 3-15 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | RAID Log, Status Report Source | Power Interest Grid, Strategy per Stakeholder | ROAM Board, Owner List |
Tagsno overlap | FlowVisual managementDelivery | RiskTrackingStakeholdersGovernance | StakeholdersFacilitationAlignmentPlanning | RiskAgileTrackingAlignment |