Agile delivery and the German Werkvertrag are often described as incompatible: one assumes evolving requirements, the other a defined result that is formally accepted. In practice, they fit together well if the sprint review is turned into a documented acceptance step. Each sprint increment is described with acceptance criteria, demonstrated, tested against those criteria and either accepted, accepted with recorded defects, or rejected with at least one named defect. This creates clarity on payment, on the burden of proof and on what happens next. This guide explains the legal mechanics of the Abnahme under BGB §640 and sets out a sprint acceptance process with a protocol template.
The numbers: more change, more need for formal acceptance
Two trends make a documented acceptance step more valuable than it was a few years ago. The first is the share of work delivered externally. Bitkom's 2025 survey found that 85% of companies report a shortage of IT specialists and that filling a vacancy takes 7.7 months on average, and the IW Köln projected in 2026 that Germany could be short of about 723,000 skilled workers by 2029. The second is the rate of change. Google's DORA 2025 report found that 90% of technology professionals use AI at work and linked AI adoption to higher throughput but lower delivery stability. GitHub's Octoverse 2025 reported that nearly 80% of new developers on the platform used Copilot within their first week. Stack Overflow's 2025 survey added that 45% of developers find debugging AI-generated code time-consuming. More change arriving faster means more risk at the moment of handover, which is exactly what a formal Abnahme is designed to control.
Why acceptance matters legally
Under a Werkvertrag (BGB §631), the Abnahme is the central legal event. Several consequences are linked to it:
- Payment: the remuneration generally becomes due on acceptance (BGB §641 Abs. 1). Where the work is to be accepted in parts and the remuneration is set for individual parts, each part is payable on its acceptance.
- Risk: until acceptance, the contractor generally bears the risk of accidental loss or deterioration of the work (BGB §644).
- Limitation period: for many types of work, the limitation period for defect claims begins with acceptance (BGB §634a).
- Burden of proof: before acceptance, the contractor generally has to prove that the work is free of defects. After acceptance, the burden for defects generally shifts to the client.
- Known defects: a client who accepts work despite knowing of a defect, without reserving rights, loses certain defect rights for that defect (BGB §640 Abs. 3). Reservations must therefore be recorded at acceptance.
Under a Dienstvertrag (BGB §611), there is no Abnahme in this legal sense, because no result is owed. A sprint review can still be documented in the same way for steering purposes, but it does not carry these legal effects.
Acceptance obligations and deemed acceptance
BGB §640 Abs. 1 obliges the client to accept work that conforms to the contract, and acceptance cannot be refused because of insignificant defects. BGB §640 Abs. 2 adds a deemed acceptance: if the contractor, after completion, sets the client a reasonable deadline for acceptance, and the client does not refuse acceptance within that deadline stating at least one defect, the work is deemed accepted.
For sprint-based delivery, this has two practical implications. First, silence is not neutral. An increment that is delivered, with a deadline set, and then ignored, may be deemed accepted. Second, a refusal must name a defect. A general statement that the increment is not good enough is not sufficient. Both points argue for a fixed acceptance window per sprint, agreed in the framework, and a protocol that forces a concrete statement.
A sprint acceptance process in five steps
- Definition before the sprint. Each item in the sprint Leistungsbeschreibung carries testable acceptance criteria and a reference to the Definition of Done.
- Delivery and demonstration. At sprint end, the provider delivers the increment in the agreed form (for example merged and deployed to staging) and demonstrates it against each criterion.
- Acceptance testing window. The client tests within an agreed window, for example a defined number of working days after the demo. The window should be realistic for the client's capacity.
- Decision per item. Each item is accepted, accepted with recorded defects, or refused with at least one specific defect.
- Protocol and follow-up. The decision is recorded in a signed or system-approved protocol. Recorded defects become tickets with a class and a target sprint.
Defect classes
A shared classification avoids arguments about whether a defect justifies refusal. The following scheme is a common pattern; adapt the definitions to your system.
| Class | Definition | Consequence for acceptance |
|---|---|---|
| A: blocking | An acceptance criterion is not met, or use of the increment for its purpose is not possible | Refusal of the affected item, stating the defect |
| B: significant | Criteria met, but a material impairment exists that requires correction | Acceptance with reservation, correction in the next sprint |
| C: minor | Cosmetic or insignificant deviation | Acceptance, item added to backlog |
Note that the contractual scheme does not override the statute. Whether a defect is insignificant within the meaning of BGB §640 Abs. 1 is ultimately a legal question. The classification helps both parties apply the same yardstick consistently.
Partial acceptance per sprint
For longer engagements, it is useful to agree in the framework that each sprint increment is subject to separate partial acceptance, with the remuneration attributed accordingly. Without such an agreement, the client is generally not obliged to accept parts of a work. With it, payment, risk and documentation follow the sprint rhythm, and no large, contested final acceptance accumulates at the end.
Where an engagement uses a fixed monthly fee, the framework should be explicit about how the fee relates to sprint acceptance, for example whether it is payable monthly against delivered and accepted increments or structured as a service component. This is a drafting decision with legal consequences that should be made deliberately.
The acceptance protocol
A protocol per sprint should contain at least:
- Engagement, sprint identifier and reference to the sprint Leistungsbeschreibung.
- Date of delivery, date of demonstration and acceptance deadline.
- Per item: identifier, decision (accepted, accepted with reservation, refused) and defects with class.
- Explicit reservations for known defects, in view of BGB §640 Abs. 3.
- Name and role of the accepting person, who must be authorised to accept.
- Agreed follow-up: target sprint for corrections, open questions.
Many teams handle the protocol inside their issue tracker, with an approval step by the authorised person. That is sufficient, as long as the framework agreement states that this form of approval constitutes acceptance and the record is retained.
Common mistakes
- Sprint reviews without any documented decision, so that acceptance status is unclear months later.
- Acceptance by people who are not authorised under the contract.
- Known defects accepted without reservation.
- No acceptance deadline, or one that the client cannot realistically meet.
- Acceptance criteria rewritten during acceptance testing.
Whichever provider you use, the process above gives both sides a reliable record and keeps the legal effects of acceptance aligned with the actual delivery rhythm.
This article provides general information and does not constitute legal advice.
Acceptance per sprint keeps the legal record in step with the delivery rhythm instead of leaving it to the end of the project. In niogod™ engagements under a Werkvertrag, the Projektleiter prepares the acceptance protocol for each sprint and your product owner records the decision. If agile delivery under a Werkvertrag is on your plan for next year, this is the model niogod™ was built around.
Talk to niogod™
Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.
Book consultation