liveBook · Manning

Time-to-aligned implementation

As explained in Spec-Driven Development

The elapsed time from an idea to the first implementation that satisfies intended behavior, construction constraints, and verification evidence.

Time-to-aligned implementation measures the elapsed time from an idea to the first implementation that satisfies intended behavior, construction constraints, and verification evidence. section 3.4.2

Time spent specifying or implementing alone does not show workflow effectiveness: verification can add time, while skipping checks can make work look faster. A short time-to-aligned implementation supports adoption, but does not show whether alignment lasts as the system evolves. section 3.4.2

How Spec-Driven Development covers it

How deep it goes
Defines the metric through behavior, construction constraints, and verification evidence, but stops short of measuring whether alignment lasts.
What you can do after
Evaluate specification-driven development by tracking idea-to-aligned-implementation time rather than specification or implementation time alone.
How it connects
Links the metric to specification-driven development and contrasts its first-implementation horizon with alignment regression.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Spec-Driven Development. The section links point to the parts of the book it draws on.