View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Working Agreements |  Agile Story Points |  Facilitation Expectation Mapping |  Team Design Team Topologies Interaction Modes |
|---|---|---|---|---|
Purposedifferent | When collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. | When teams want to rate complexity rather than hours, it creates a shared, relative scale. It sorts work by value, risk, and delivery ability. The result is captured as Point Estimates, Reference Stories, and Velocity Data. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | When several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 45-90 min | laufend, 1-5 min je Item | 45-90 min | Half day |
Participantsdifferent | 3-12 | 3-9 | 3-12 | Team-Leads plus Architecture |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Working Agreements, Team Norms, Review Cadence | Point Estimates, Reference Stories, Velocity Data | Expectation Map, Alignment Notes, Agreements | Interaction Heat Map, Agreements per Pair |
Tagsno overlap | TeamCollaborationAgile | EstimationAgileMeasurement | AlignmentStakeholdersTeam | TeamAlignmentCollaborationOrganization |