Run it in a Team
Agile is no longer agile enough.
Agile was the answer to waterfall. It made humans faster. But the team has changed — it’s humans and AI agents now, moving at machine speed. The bottleneck moved from execution to direction, and agile’s human-paced ceremonies became the drag. C² is the operating model for that team.
01The Diagnosis
Agile is a human coordination protocol
Every piece of agile machinery exists to coordinate people. Two-week sprints timebox human work. Daily standups sync humans and surface blockers. Story points predict human throughput. Retros improve the human team. It was the right answer for its era — small teams, short loops, working software over documentation.
None of that was wrong. It was built for a team made entirely of humans, shipping at human speed.
02What Changed
The bottleneck moved
AI agents collapsed execution time. The thing agile optimised — human coding throughput and the coordination of human developers — is no longer the constraint. An agent ships a feature in a session. The constraint is now direction: the brief, the context, the review, the quality bar.
At machine speed, the ceremonies stop being acceleration and become friction:
- 01You hold a daily standup about work an agent finished — and forgot — overnight.
- 02You estimate in story points a task the agent did in an hour.
- 03You batch into a two-week sprint what now flows session by session.
- 04You schedule a retro to improve a team whose fastest members don't attend meetings.
Agile sped up humans. When the team moves at machine speed, agile’s human-paced ceremonies are the bottleneck.
03Keep the Spirit
Keep the spirit. Replace the machinery.
“Agile is dead” is the wrong call — and it isn’t true. Agile’s principles endure: tight feedback, working software over rotting docs, responding to change over following a plan, individuals and interactions over process. C² keeps all of it.
What C² replaces is the human-paced coordination layer — the meetings and cadences built for a team of people. The spirit survives the shift to machine speed. The ceremonies don’t.
Kept — the spirit
- Tight feedback loops
- Working software over documentation
- Respond to change over follow a plan
- Individuals & interactions — now human ↔ AI too
Replaced — the machinery
- Two-week sprints
- Daily standups
- Story points & velocity
- Calendar-based ceremonies
04The Shift
Coordination moves from meetings to the contextbase
Agile coordinates the team through synchronous human events on a cadence. C² coordinates the team through the contextbase— git-native, continuous, and machine-readable, so humans and agents read the same source. The standup becomes a brief the next agent reads cold; the plan lives in PRDs the agent inherits; the retro becomes a review plus the Learn loop. The team’s nervous system stops being calendar-based and becomes repo-based.
| Agile — human era | Why it existed | C² — human + AI era |
|---|---|---|
| Sprint (2 weeks) | timebox human work, force shipping | The session — the agent's iteration unit; work flows continuously |
| Daily standup | sync humans, surface blockers | Session Brief — async, written, read by humans and AI |
| Story points / velocity | predict human throughput | Brief quality + merge discipline — the new bottleneck and metric |
| Backlog grooming | manage human WIP | Principles A & B — keep the cockpit small, brief before flying |
| Retrospective | improve the human team | Principle E + the Learn loop — compound into the contextbase |
| Sprint review / demo | show humans the increment | Release Notes / Weekly Announcement — committed, not performed |
| Role: contributor | write the code | Role: pilot — direct, review, own the quality bar |
Agile’s ceremonies were how humans stayed in sync. In C², the contextbase keeps humans and agents in sync — continuously, in writing, in git.
05So, Do We Still…
Do you still need standups and retros?
The honest answers, ceremony by ceremony:
Daily standup?
No meeting. The Session Brief replaces it — async and written, surfacing what was done, what's blocked, and the next start state. Read by the next human or agent, cold. The standup's job survives; the meeting doesn't.
Sprint planning?
Continuous, not boxed. Work is scoped in Feature PRDs and Prompt Briefs as it's needed, not batched into a fortnight. The Cascade is the plan.
Backlog grooming?
Replaced by the principles, not a ceremony. Fly the plane keeps the cockpit small — a WIP cap, typically five in-progress PRDs; No takeoff without a flight plan blocks a PRD from going active without a brief. The folders enforce it.
Retrospective?
Yes — but reframed. A short monthly review walks every in-progress PRD and retires the stale ones, and the Learn loop — Every flight makes the next one better — consolidates what the team discovered into the contextbase. You improve the system of record, not just the team's feelings.
Sprint review / demo?
Release Notes and the optional Weekly Announcement. Shipped work is recorded in git, not performed in a meeting.
Any human meetings at all?
Keep one: a light, periodic team alignment — direction, priorities, the things humans genuinely decide together. Everything that was just re-syncing people who could have read a brief is gone.
06Decision
You’re all pilots now.
The team is humans and agents, moving at machine speed. Stop coordinating it with meetings built for a slower team. Move the coordination into the contextbase, keep the few ceremonies that set direction and reflect, and let the work flow session by session.
Going deeper on the thesis? Read: an alternative to Agile for AI-native teams.