References

Field test

From ticket to pull request: 162 hours become 64

A field test in one of our own projects: in one sprint, engineers implemented 14 real tickets in dialogue with a coding agent and estimated the effort with and without it. Around 60% less effort, with big differences per ticket.

Field test

Challenge

An SII team develops and runs a long-lived business application for a car manufacturer - a classic brownfield project. Tickets, from bug fixes to new features, were implemented by hand and estimated in story points. The question for our field test: how much effort does a coding agent save in a brownfield project like this, without compromising quality or accountability?

Approach

Not an autonomous agent but guided agentic development: the engineer works in dialogue with the agent and steers every step.

  • Agent environment for ticket work - system prompt, skills for bug fixing, logging and CI, connections to ticket system and code repository.
  • From ticket to pull request in dialogue - the agent reads ticket and logs, explores the code base, proposes a plan and implements it; the engineer discusses, corrects and asks for rework.
  • Checks before review - every change passes unit tests or an error-free build before a pull request is created.
  • Humans decide - engineers review every pull request and decide on the merge.
  • Measurement - for each ticket, effort without the agent (story-point estimate) and with the agent (engineers’ own estimate) was recorded.

How the collaboration worked

deterministicagentengineer (in dialogue)
Agent environment: system prompt · skills (bug fixing, logging, CI observer, PR viewer) · connections (ticket system, code repository, library docs)
Engineer: “Look at ticket-1234”
→
Fetch ticket and logs via connection
→
Explore code base, propose plan
→
Engineer: discuss and correct the plan
→
Implement
→
Check: unit tests or error-free build
→
Engineer: check result, ask for rework
→
Git commit, pull request
→
Engineer: review and merge
The engineer steers in dialogue and decides at every point, the agent does analysis and implementation, tools check deterministically

Result

  • 14 tickets: 162 hours estimated manually → 64 hours with the agent, as estimated by the engineers (≈ -60%).
  • Small, standardised tickets: ≈ -93%. Large, complex tickets: ≈ -18%. The effect depends heavily on the ticket.
  • No change without passing tests and human review.

Results per ticket

By ticket type · effort-weighted
Bug (6)
93%
Task (2)
89%
Improvement (3)
35%
Feature (3)
51%
By ticket size · effort-weighted
small (10)
93%
medium (3)
51%
large (1)
18%
TypeSPmanual (h)with agent (h)saving
Bug25.60.2596%
Bug38.40.594%
Bug25.60.2596%
Bug38.40.594%
Feature822.41055%
Task38.4188%
Feature514193%
Bug38.40.7591%
Task25.60.591%
Bug25.60.591%
Improvement25.60.2596%
Improvement25.60.591%
Feature822.41820%
Improvement1336.43018%
Total58162.46460.6%
Manual: story points × 2.8 h · with the agent: self-assessed by the engineers · one project, March 2026. Mean per ticket 79.5%, effort-weighted 60.6% - we quote the lower figure

Field test in one sprint (March 2026) in one of our own projects, 14 tickets of mixed type and size. Guided work in dialogue, not an autonomous agent. Manual effort from story-point estimates; effort with the agent self-assessed by the engineers. A small sample with estimated shares - a practice experiment, not a study. Models have improved since.

* Field test: measured in one of our own projects

Part of the SII Germany team

Let’s
talk.