methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of Team API with its method-specific working model.
Team Design
Team API
Paper illustration of Shape Up with its method-specific working model.
Delivery
Shape Up
Paper illustration for RAPID
Decision Making
RAPID
Paper illustration for Delegation Poker.
Facilitation
Delegation Poker
Purposedifferent
When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document.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.In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels.When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice.
Complexitydifferent
LowMediumMediumLow
Timedifferent
Half day initial, dann laufend6 Wochen Cycle + 2 Wochen Cool-Down45-90 min45-90 min
Participantsdifferent
Ein Team plus Stakeholder2-4 pro Pitch3-123-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Team API DocumentPitches, Bet-table decisions, Hill charts, Cooldown outcomesRAPID Role Map, Recommendation, Decision LogDelegation Board, Decision Boundaries, Role Agreements
Tagsno overlap
TeamAlignmentCommunicationService
PlanningDeliveryAutonomy
DecisionRolesGovernance
AutonomyRolesTeam
Add more methods