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 Affinity Estimation | ![]() Domain Modeling Domain Context Map | ![]() Facilitation Stakeholder Mapping | ![]() Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | When many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes. | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 30-90 min | 1-3 h | 60–90 min | 60-90 min |
Participantsdifferent | 3-12 | 3-10 | 2-8 | 3-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Affinity Size Map, Grouped Estimates, Unclear Items | Domain Context Map, Boundary Notes, Ownership Map | Stakeholder Map, Engagement Plan, Risk Notes | Salience Diagram, Strategy per Class |
Tagsno overlap | EstimationBacklogRelative sizing | Domain-Driven DesignContextBoundaries | StakeholdersAlignmentFacilitationChange | StakeholdersFacilitationAlignmentGovernance |



