Agent Driven Development

Scrum is dead. Agents don’t do stand-ups.

For twenty years, I protected the process. Now the process runs without me in the room.

Read the talk
QR code linking to https://julia.rustgrid.com Scan to follow along julia.rustgrid.com

Where I come from

Twenty years in the room

Stand-ups facilitated, give or take
≈5,000
Sprints planned, reviewed and closed
≈500
Question I can no longer avoid: what is my job when agents build?
1
  1. Shift 1

    Waterfall to Scrum

    Gantt charts gave way to stand-ups, boards and two-week promises.

  2. Shift 2

    Releases to flow

    Palo Alto and Mountain View, 2011–2015: shipping became continuous.

  3. Shift 3

    People to agents

    On RustGrid, agents already do the building.

Every shift felt like the end of my job. Each time, the job moved up a level. This is the third time.

1 · Why Scrum breaks

Each ceremony becomes a step a machine can check

Every Scrum ceremony solves a human coordination problem. Agents don’t have those problems. They have cost, correctness and security problems.

2 · The ADD framework

ADD at a glance

Spec artifacts are the source of truth
4
Quality gates every change must pass
6
Model tiers, with a human as the last stop
4 + 1

2 · The ADD framework

Six gates, cheapest first

  1. Static

    Format, lint, type check, constraint policies

  2. Security

    SAST, secret scanning, dependency audit, prompt-injection checks

  3. Architecture

    ADR compliance, module boundaries, forbidden dependencies

  4. Tests

    Generated acceptance tests and coverage thresholds

  5. Documentation

    Docs, API reference and changelog updated

  6. Runtime

    Preview deploy, smoke and performance budgets, progressive rollout

Agents open pull requests. They never merge, change pipelines or touch secrets.

2 · The ADD framework

Expensive models are an escalation, not a default

  1. Tier 0No model
  2. Tier 1Small model
  3. Tier 2Mid model
  4. Tier 3Frontier model
  5. Last stopHuman

Fail a gate: retry once with the error, then move up one tier. Task types that pass reliably move down a tier.

2 · The ADD framework

Eight rules the framework stands on

  1. Constraints over conversations

    If a rule matters, a gate can check it.

  2. Specs are the product

    Humans write specs. Code is an output.

  3. Tests before code

    Criteria become tests before an agent starts.

  4. Minimum viable model

    The cheapest model that meets the bar.

  5. Gates, not reviews

    Humans review exceptions, not every change.

  6. Secure by construction

    Least privilege. No secrets in prompts.

  7. Everything is traceable

    Code links back to spec, model and cost.

  8. The loop tunes itself

    Failures improve constraints and routing.

What I take with me

What I keep, what I let go

  • Keep: people first

    Agents build. People decide what is worth building.

  • Keep: short feedback loops

    Gates answer in minutes, not at the next retro.

  • Keep: honesty about done

    Done is a gate result, not an opinion.

  • Let go: story points

    Measure real cost and quality, not guessed effort.

  • Let go: status meetings

    The pipeline already knows the status.

  • Let go: dragging cards

    If a person sets the status, it is already out of date.

Scrum taught me to inspect and adapt. Now it’s Scrum’s turn.

Thank you.

Back to the QR code