View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Polarity Mapping |  Agile Acceptance Criteria Workshop |  Delivery RAID Log |
|---|---|---|---|
Purposedifferent | Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-2 h | 20-40 min pro Story | 30 min Setup, dann laufend |
Participantsdifferent | 3-12 | 3-6 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop | Workshop | Async |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | Acceptance Criteria, Story Update | RAID Log, Status Report Source |
Tagsno overlap | Systems thinkingTradeoffsLeadership | AgileRequirementsRefinementBehavior-Driven Development | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
