zero gravitySOLUTIONS
← All insightsENGINEERING PARTNERSHIPS / ACCEPTANCE AGREEMENT

Agree on what delivered really means

QUICK ANSWER

A shared definition of done should connect the customer journey to behavioral, release, and operating evidence. Separate task completion from feature acceptance and customer availability. Record the accepted revision, environment, exceptions, and decision owner so progress means the same thing to client and team.

Inside this article 5 sections

A shared definition of done tells the client and engineering team what evidence must exist before a capability is considered delivered. It should distinguish code completion, release readiness, customer availability, and operational ownership. Combining those states into one checkbox makes progress look simpler while moving unresolved work into the gaps.

Start with a capability that crosses several systems, such as a customer-facing data export. The API, background worker, storage policy, download experience, monitoring, and support procedure may arrive through separate changes. Each change can be merged while the complete capability remains unavailable.

Separate task state from product state

A task can be complete when its narrow acceptance conditions pass. A feature can require several completed tasks plus integration evidence. A release can package multiple features while keeping some disabled. Use names that reflect these different objects instead of asking one board column to represent them all.

For the export capability, “worker merged” means the worker implementation entered the main branch under the team's code-review rules. “Ready for release” means the intended artifact and configuration can operate together. “Available to customers” means eligible users can reach the capability in the intended environment. Each statement should have its own evidence.

This distinction also improves financial visibility. If engineering work is complete but acceptance waits for client data or a provider approval, record the dependency and remaining responsibility. Avoid presenting waiting as active implementation or quietly moving the unfinished obligation outside the forecast.

Build an evidence map around one user journey

ORIGINAL DELIVERY EVIDENCE MAP / ACCOUNT EXPORT
Behavior acceptedA permitted user receives the correct account data; an unauthorized user does not.
Failure understoodInterrupted work has a visible state and a tested recovery path without duplicate effects.
Release preparedThe artifact, configuration, migration order, and stop conditions are identified.
Operation ownedAn owner can diagnose a late export, control access, and explain storage costs.
Customer availableThe intended audience can use the released capability and find relevant guidance.
Evidence follows the complete journey. A passed unit test supports one part of the claim; it does not replace the release and ownership conditions.

Make the behavioral conditions concrete. A fixture can include two accounts with different records, an expired export, a failed storage request, and a repeated download request. Record expected results before the team demonstrates the implementation. Otherwise a polished demonstration can accidentally redefine success around whichever path currently works.

Include nonfunctional requirements that materially affect the promise. If a large export must run without blocking interactive API requests, define the workload and evidence needed to assess that boundary. Avoid adding a generic performance checkbox with no operation, load shape, or acceptance criterion.

Keep the evidence proportional. A minor wording correction should not require a full disaster-recovery exercise. A new asynchronous billing operation needs substantially more failure and reconciliation evidence. Agree on a common baseline and add capability-specific conditions where the risk or product contract requires them.

Store acceptance as a versioned record

Attach acceptance to a defined change and environment. A useful record includes capability identifier, acceptance version, artifact revision, environment, required evidence, open exceptions, and decision owner. When a substantial behavior changes, update the conditions and review the new evidence instead of inheriting an old approval silently.

For an illustrative release, the record might say that export schema version three was validated against fixture set seven in staging, with production enablement limited to an agreed audience. That identifies what was checked without claiming that every future schema and account type is covered.

Do not store screenshots as the only evidence of behavior that should be reproducible. A screenshot can show an interface state, but the underlying permission or retry invariant usually needs an executable check, a trace, or a controlled exercise. Link to the authoritative result and retain enough context to rerun it.

Where a client accepts an exception, record the consequence and owner. “Monitoring later” is vague; “No automated alert for exports older than the agreed interval until the next milestone; support checks the backlog each business day” exposes the temporary operating choice. The client can then decide whether that condition is acceptable.

Coordinate client decisions with engineering progress

Identify who can approve user-facing behavior, operating readiness, and any commercial scope change. One person may hold several roles, but the decision types remain different. An engineer confirming a test result does not necessarily authorize a changed customer promise or an additional expense.

Give reviewers a bounded decision packet: the capability, acceptance conditions, result, open exceptions, and requested decision. Link to deeper evidence without requiring every stakeholder to read a full implementation diff. Keep technical approval with qualified reviewers while making the product decision understandable to the client.

Plan acceptance time as a delivery dependency. A team cannot reliably finish a milestone on Friday if the only approver is unavailable for two weeks. Agree on review windows and a route for unresolved questions. Silence should not automatically become acceptance unless the parties have deliberately established that process.

Keep the definition useful after launch

After release, check whether the delivered capability meets the stated purpose and whether support can operate it. Observed failures should become specific follow-up work or defects against the accepted contract. Do not keep reopening an entire milestone because a new enhancement has become desirable.

Use incidents and delivery friction to improve the shared definition. If repeated releases omit migration recovery, add a targeted requirement for relevant database changes. If the checklist becomes so broad that every item is marked without inspection, remove irrelevant ceremony and make the meaningful conditions easier to verify.

A definition of done is most effective when it protects a shared understanding of value. The client sees what has been accepted and what remains; the team sees the evidence required to finish. The handover rehearsal tests continuing ownership, while the operating agreement establishes everyday visibility. Our dedicated teams use these agreements to keep implementation, acceptance, and operation connected.

FROM INSIGHT TO ACTIONDedicated development teams

Make delivery visible beyond the merged pull request.

Our dedicated teams connect implementation, acceptance, deployment, and operational handover in one understandable delivery agreement.

Explore dedicated teamsDiscuss your team

Start with your goals.
We’ll work through the next step together.