If the screen comes first, the room debates colour. If the process is unwritten, the software makes the exception in an email permanent. A software discovery sprint is short and bounded: a few working days, one flow, a written result. It is not an open-ended analysis contract.
The result is not a screen
The result is a flow. The event that starts it, the role that looks, the approval, the exception, and the record that means done. A request to make the panel pleasant is not in that result. The steps that already run in a spreadsheet are. An invented flow collapses in the first week of release.
When a sprint is worth opening
Open it when the same job runs every week through sheets, email and phone, and the cost of the error is visible. If the process changes with every customer and nobody will name the flow, decide internally first. A sprint does not encode indecision.
Written scope closes before drawing
The written scope separates steps in the first release, steps left on the queue on purpose, and systems nobody will touch. If the work does not replace the ERP, that sentence sits in the sprint note. Which field is read and which is written back is known when discovery ends.
Handover is inside discovery
Code ownership stays with the company. That sentence is written before anyone approves a screen. Whose name is on the repository, the environment and the sample data goes into the note. Account ownership is named there too. HED Creative is the accountable partner in Berlin and Ankara. Discovery is not a presentation that stretches the sale. It ends as a project, or as a deliberate decision to wait.
To have the flow written, the IT partner brief is enough. The contract shape of the result: website scope document.