9. Core Principles

Dandori rests on four foundational principles.

The Specification Is the Unit of Work

In Scrum, the unit of work is the user story. In Dandori, it is the specification. A specification is a structured, precise document that serves simultaneously as the design document, the AI execution instruction, the review criteria, and the team communication medium. Every other element of the framework exists to optimize the creation, execution, and validation of specifications.

Human Judgment Is the Scarce Resource

Scrum treated developer time as the scarce resource and built its entire coordination model around allocating and protecting that time. Dandori treats human judgment as the scarce resource: the ability to specify precisely, decide quickly, review effectively, and maintain architectural coherence across a system that AI agents are changing rapidly. Every ceremony, role, and practice in the framework exists to amplify and protect human judgment.

Preparation Determines Quality

This is the principle that gives the framework its name. In the Toyota Production System, dandori refers to the meticulous preparation work done before production begins. Toyota discovered that investing in better preparation reduced waste, rework, and cycle time far more than optimizing the production line itself. The same principle applies to AI-augmented development: the quality of the specification determines the quality of the output. Investing in better specs pays more than investing in better AI tools or faster execution.

Flexible Constraints

A framework has to be flexible, but it also has to restrict. If you push here, there will be a constriction. If you push there, there will be an expansion, but it will only fit a certain amount. This is the design principle that separates a framework from a recipe book and from anarchy.

Scrum failed not because it was too rigid but because it was too permissive. It defined ceremonies, roles, and artifacts but allowed organizations to reinterpret every one of them until "doing Scrum" meant whatever you were already doing. The flexibility that was supposed to make Scrum adaptable made it meaningless.

Dandori takes a different position. Certain elements are non-negotiable: the separation between Spec Owner and Reviewer, the Pipeline Sync, the Spec Handoff, the Integration Review. These exist because removing them breaks the quality model. Other elements are adaptive: sprint boundaries, ceremony frequency, the specifiability classification thresholds. These can be adjusted based on data and team experience.

The distinction is explicit. The ceremony classification system (Non-Negotiable, Required with Adaptive Frequency, Conditionally Required, Earned Optional) is the mechanism by which Dandori says "you can adjust here, but not there." This is not arbitrary rigidity. Each constraint exists because a specific failure mode occurs without it. Each flexibility exists because different teams legitimately need different configurations.

The principle applies beyond ceremonies. The three roles (Spec Owner, Reviewer, Prioritizer) are non-negotiable as functions, but who fills them is flexible. The five lifecycle stages are non-negotiable as a sequence, but how long each stage takes is flexible. The metrics are non-negotiable as instruments of visibility, but the specific targets are flexible.

This is how Dandori avoids Scrum's fate. By being explicit about what bends and what does not, the framework maintains its coherence even as teams adapt it to their context. If adoption can mean anything, adoption means nothing. Dandori defines what adoption means.