A piece of work can leave the board and still be unfit for the person who needs it. The column says finished. The quality bar was never written down, so finished means whoever touched it last was ready to stop. The next argument is about the status, not about the work.
Ken Schwaber and Jeff Sutherland put the bar in the 2020 Scrum Guide. The definition of done is a formal description of the state of the increment when it meets the quality measures the product requires. The moment a backlog item meets that description, an increment is born. Work cannot be part of an increment unless it meets the definition. An increment has to be usable if it is to provide value.
What unfinished work is allowed to do
If an item does not meet the definition, it cannot be released and it cannot be presented at the review. It goes back to the backlog for later. The review is not a gate that value must wait for. An increment may reach the people who need it before the review happens. The constraint is the definition, not the meeting. A workshop that rehearses the review, and lets unfinished work be shown there, has inverted the rule. Showing it does not make it done. Sending it back is the move the guide requires.
The point of the definition is a shared view. The guide's artefacts are meant to give everyone who inspects them the same basis for a decision. Where transparency is low, decisions follow that diminish value and raise risk. Inspection without transparency is misleading and wasteful. Inspection that never leads to a change is pointless. A private meaning of finished, held by the last person who touched the work, is the low-transparency case.
Who has to share the bar
If the definition is already an organisational standard, every team follows it as a minimum. If it is not, the team writes one that fits the product. The people doing the work are required to conform to it. Where several teams work on one product, they define one definition and they all comply with it. A workshop that lets each table invent a private checklist, and never reconciles them, will produce the opposite of the shared view. Two teams will call the same gap finished and unfinished.
Leaving a piece of the framework out is not a harmless shortcut. The guide says that changing the core, dropping elements or ignoring the rules covers up problems and limits the benefit. A session that teaches the events and never writes the definition has dropped the commitment attached to the increment. Unfit work gets harder to see, because finished has been left to whoever is speaking.
What the agenda gives away
A weak proposal uses a fictional team and ends with a poster of roles. Done appears as a slide of quality words that nobody applies to live work. The test is smaller. Take one item the board already calls finished. Mark the conditions it fails. Send it back. If every item on the wall is already done, or done is whatever the last person says, the day will not change the meaning of the column. Cutting scope so a slice can move is a different question. A small slice can still be unfit to show.
Collective Campus is building high-performance culture and teams for the AI world. The agile workshop is for a team that can bring live work and is allowed to send an item back when it fails the bar. What to ask when the ceremonies already run is in how to judge the day by the live slice. What changes when the meeting stands in for the work is in agile without the theatre. What a team should put under test once the slice is a bet is in a lean startup workshop for corporate teams.
What to bring
Bring one piece of work the board calls finished, and the conditions you are willing to write down. If nothing is allowed to return to the list, the definition has nothing to decide.
