Who wants to be the first to test it?
Five articles of theory and practice now lie behind this series. The last one is neither — it is an invitation.
Five articles now lie behind this series. Why Scrum is reaching its real end. Why SAFe answers a coordination problem with even more coordination instead of solving it. Three axes along which every development method can be measured. Eight months of building alone, with everything that actually went wrong. And a tool that makes its own methodology checkable against itself.
This last article is no longer a theory article. It is an invitation.
What exists right now — and what deliberately does not yet
Requirements Dialogue is documented openly: the four epistemic states, the dialogue between two structurally separated roles, the hard completion criterion per requirement alongside unlimited openness at the corpus level, additive rather than overwriting correction. Anyone who wants to follow, discuss or apply this in their own setting will find the foundations already.
CCIDE, the tool on which the methodology is taking shape and proving itself, is in active development. There is no public version to download yet. What there is, is a project that shows honestly what it is working on, which errors have already occurred, and which questions are still open — instead of pretending everything is finished.
Three ways to be involved already
Anyone who wants to use the methodology on their own project or team can start early — not with CCIDE itself, but with the Requirements Dialogue approach as such. The four building blocks can be tried out in your own requirements process without the finished tool, using your preferred AI tool as the Refiner and a second, deliberately freshly started instance as the checking instance.
Anyone who wants to join the discussion on the substance — as a practitioner, as a researcher, as someone with a different perspective on the same three axes — is invited to do so directly. An approach that describes itself as unproven in parts lives on exactly this kind of exchange, not on tacit agreement.
And anyone who would like to be there early when CCIDE itself becomes usable can get in touch now. We are looking for ten pilot testers who will get early, free access — deliberately a small, fixed number, because a tool that is still working on itself benefits more from a few attentive first users than from many at once.
The starting point for all of it
At the beginning of this series stood a simple observation: software projects rarely fail because of bad code. They fail because nobody knew precisely enough what was actually needed — and because that gap only surfaces late, when correcting it is already expensive. Requirements Dialogue is an attempt to keep that gap smaller from the start, not through more process but through a mechanism that actually checks instead of merely hoping.