Why discovery if it's already clear
Overruns almost never start in the sprint. They start in a vague goal: no result owner, no boundaries, no “done” criterion. Discovery fixes what must change in the business — before estimation and code.
Artifacts
Minimum: goals, users, constraints, current systems and integrations. This is enough to distinguish scope from wishlist and not estimate “by eye”.
Readiness criteria vs wishlist
Acceptance criteria describe an observable outcome. Wishlist describes wishes without boundaries. The spec retains the former; the latter goes into the roadmap.
From discovery to a fixed estimate
When boundaries and acceptance are clear, you can lock cost and timelines based on the agreed scope. Scope changes after that – in writing, not as a “gray zone”.
Checklist before start
There is a result owner, integration map, readiness criteria, risks and a milestone calendar. If not – we don’t start development, even if “very urgent”.