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 |  Decision Making Eisenhower Matrix |  Decision Making Pareto Analysis |
|---|---|---|---|---|
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. | It separates true priorities from noise so it becomes clear what should be done now, scheduled, delegated, or dropped. | In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 30-90 min | 15-30 min | 30-60 min |
Participantsdifferent | Designers, developers as users, and facilitation | 3-12 | 1-6 | 1-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | 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 | Eisenhower Matrix, Action List, Delegation Notes | Pareto Chart, Top Causes, Focus List |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | PrioritizationScopeDecision | PrioritizationFocusTasks | PrioritizationQualityFocusRoot cause |