About VDD Methodology

Why VDD was created

Verification-Driven Delivery Methodology did not start as a theory looking for a problem. It emerged from running engineering teams through the shift AI brought to software delivery: watching billed hours stop being an honest unit of value as code generation got faster, and watching verification quietly become the real bottleneck while nobody priced it as such. Traditional delivery models reward time spent, even when AI compresses the work itself. Verification-based delivery rewards the work that actually determines whether software is correct, usable, and ready to ship. VDD is the attempt to name that shift precisely enough to build a delivery method around it, rather than around whichever tool happens to be fastest this year.

The goal was never a proprietary process kept inside one company. A methodology that only one company can use is not a methodology; it is a sales pitch. VDD is published openly, with a public specification anyone can read, apply inside their organization, and hold their own delivery against, so it can outlast any single vendor's roadmap, including ours.

The author

Alexander Lipanov

PhD, Applied MathematicsVDD Methodology AuthorFounder & CTO, SOFYCOD

Alexander Lipanov created VDD. He has 35 years of experience in engineering, research, and software development, including 25 years as an IT entrepreneur who built and led international engineering teams.

He holds a PhD in Applied Mathematics and has published more than 30 scientific articles and one patent, including research on image normalization, computer-vision control of aircraft landing, and control architectures for mobile robots and drones.

Before VDD, he reviewed documents, methods, and algorithms in the CISQ work that became ISO/IEC 5055, the international standard for measuring software quality. He is the founder and CTO of SOFYCOD.

More writing: alexlipanov.com →

Stewardship

Verification-Driven Delivery Methodology was created by Alexander Lipanov. All rights in it are owned by Sofycod Sp. z o.o., its sole steward, responsible for the official text, its versioning, and the uses permitted under the Licensing & IP Policy. No other individual or organization maintains, certifies, or governs VDD.

Keeping stewardship with one accountable organization, rather than an open, unmanaged committee, is a deliberate choice: the specification can move quickly while still having one clear place to resolve ambiguity, register objections, or propose changes, rather than fragmenting into incompatible dialects.

Historical Origins and Lasting Relevance of the Practice

VDD's origin is practical, not academic. It was shaped within real engineering teams that decomposed delivered features into countable units, calibrated pricing against actual historical revenue, and watched where independent verification broke down when it was skipped, before any of it became a written specification. That is also why the Specification and the Implementation Playbook are separate documents: one states the methodology, the other reflects how teams have applied it so far.