View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Context Canvas |  Delivery Shape Up |  Operations Time Blocking |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | When an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency. | Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts. | With a calendar that grows on request, the method makes available time explicit again. It combines appointments, focus work, and buffer into a more realistic day structure. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 6 Wochen Cycle + 2 Wochen Cool-Down | 15-30 min Planung, laufend | 20-40 min pro Story |
Participantsdifferent | 3-10 | 2-4 pro Pitch | 1 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop |
Outputdifferent | Context canvas, Open questions, Shared context notes | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Blocked Calendar, Capacity View, Focus Plan | Acceptance Criteria, Story Update |
Tagsno overlap | ContextFramingRequirementsCanvas | PlanningDeliveryAutonomy | PlanningTime managementFocus | AgileRequirementsRefinementBehavior-Driven Development |