A precise problem, a testable system, a decision based on evidence.
A short cycle with an agreed scope, criteria written before building and a documented decision.
At a glance
Who it is for : Teams that want to test an answer to a precise problem.
Starting point : A need, data and an expected outcome.
What you receive : A testable building block and a documented evaluation.
What is not delivered : A system in production at scale, a promise of a fixed deadline.
How we decide : With your users, against the scoping criteria.
Possible next step : Move to production, correct or stop, and why.
Scoping
Need, expected outcome, data and success criteria written before building.
Construction
A building block that runs on your real cases.
Evaluation
With your users, against the scoping criteria.
Decision
Move to production, correct or stop, and why.
Deliverables
A demonstrator, evaluation criteria, a summary of gaps, a decision and next steps.
Limits
Duration depends on the problem and is set during scoping. The sprint does not deliver a system in production at scale or promise a fixed deadline.
Frequently asked questions
What should we prepare?
The need, cases to test, accessible data and the people who will evaluate the outcome.
Is production automatic?
It depends on test results and the decision made with you.
Journal
What a pilot skips to look finished
In June 2025, Gartner checked how many self-described agentic AI products could actually plan and execute a task without a human approving every step. Out of thousands claiming to, it counted about 130. The same report expects more than 40% of the projects built around the rest to be canceled by the end of 2027.
The claim a green pipeline never makes
A pull request with no code in it. A dashboard as quiet as a slow Sunday. A test suite that stayed green because the thing it was testing never ran. Three of our own systems reported success this month, and none of them had earned the word.