View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Delivery MoSCoW |  Delivery Cost of Delay |  Product Strategy ICE Scoring |
|---|---|---|---|---|
Purposedifferent | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | When a release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved. | 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. | When ideas need sorting quickly, it condenses impact, confidence, and effort into one compact score. It connects customer value, product logic, and decision priorities. The result is captured as an ICE table and top-ideas list. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 30-90 min | 90-180 min | 30-60 min |
Participantsdifferent | Designers, developers as users, and facilitation | 3-12 | 3-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Prioritized Backlog, Release Scope, Tradeoff Notes | CoD Table, Prioritization Sequence | ICE Table, Top Idea List |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | PrioritizationScopeDecision | PrioritizationDeliveryEconomicsDecision | PrioritizationScoringGrowthDecision |