14. Relationship to Existing Methodologies

Relationship to Agile

Dandori is fundamentally Agile in its values. Where it diverges is in investing heavily in upfront specification because the cost of iteration has changed. Both positions are empirically driven responses to the economics of their era. Agile was right for 2001. Dandori is right for 2026.

Parallels with Scrum

Dandori preserves Scrum's definition of done (as acceptance criteria), sprint review (as Integration Review), retrospective (retargeted at human-AI collaboration), and role clarity.

Differences from Scrum

The atomic unit shifts from time (sprint) to specification. Estimation transforms into specifiability assessment. The team composition evolves to emphasize specification and AI collaboration skills.

Parallels with Kanban

Dandori has the strongest kinship with Kanban: focus on flow, WIP limits, and measuring cycle time.

Differences from Kanban

Dandori is more opinionated than Kanban, defining specific roles, lifecycle stages, and cadences to address failure modes that pure Kanban does not.

The Synthesis

Dandori inherits Agile's philosophy, borrows Kanban's flow mechanics, preserves Scrum's role clarity and cadence discipline, and adds a new layer: the specification as a first-class artifact that serves as design document, AI execution instruction, review criteria, and team communication medium simultaneously.