Compare

View methods side by side.

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

Selected:SAAM (Software Architecture Analysis Method)Cost of Delay Ivy Lee Method Force Field Analysis

Criterion	Architecture SAAM (Software Architecture Analysis Method)	Delivery Cost of Delay	Operations Ivy Lee Method	Decision Making Force Field Analysis
Purposedifferent	SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.	Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence.	With a restless workday full of too many open items, the method creates radical simplicity. It directs attention to a short sequence instead of a broad, still-open field.	In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.
Complexitydifferent	High	High	Low	Low
Timedifferent	Preparation, scenario analysis, and findings review; effort depends on scope	90-180 min	5-10 min daily	45-90 min
Participantsdifferent	Architecture experts and stakeholders for scenarios and weighting	3-8	1	3-12
Formatdifferent	Workshop + async	Workshop	Async	Workshop
Outputdifferent	Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives	CoD Table, Prioritization Sequence	Daily Priority List, Completion Notes	Force Field Map, Change Levers, Risk Notes
Tagsno overlap	ArchitectureChangeAnalysisComparisonQuality	PrioritizationDeliveryEconomicsDecision	PrioritizationProductivityExecution	ChangeDecisionStrategy

Add more methods