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 |  Delivery RAID Log |  Agile Specification by Example |
|---|---|---|---|
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. | 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 business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-2 h | 30 min Setup, dann laufend | 60-90 min pro Feature |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | 3-6 |
Formatdifferent | Workshop | Async | Workshop |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | RAID Log, Status Report Source | Example Table, Acceptance Tests |
Tagsno overlap | Systems thinkingTradeoffsLeadership | RiskTrackingStakeholdersGovernance | AgileRequirementsExamplesBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
