𝘾𝙖𝙣 𝘼𝙄 𝙖𝙜𝙚𝙣𝙩𝙨 𝙢𝙖𝙠𝙚 𝙤𝙪𝙧 𝘼𝙜𝙞𝙡𝙚 𝙩𝙚𝙖𝙢𝙨 𝙛𝙖𝙨𝙩𝙚𝙧?

Most organizations think the big question is:
“𝘾𝙖𝙣 𝘼𝙄 𝙖𝙜𝙚𝙣𝙩𝙨 𝙢𝙖𝙠𝙚 𝙤𝙪𝙧 𝘼𝙜𝙞𝙡𝙚 𝙩𝙚𝙖𝙢𝙨 𝙛𝙖𝙨𝙩𝙚𝙧?”
They’re asking the wrong question.

Human‑centric Agile and agent‑driven systems are not interchangeable; they optimise for different kinds of intelligence. 𝘼𝙜𝙞𝙡𝙚 𝙩𝙚𝙖𝙢𝙨 𝙖𝙧𝙚 𝙨𝙤𝙘𝙞𝙖𝙡 𝙡𝙚𝙖𝙧𝙣𝙞𝙣𝙜 𝙨𝙮𝙨𝙩𝙚𝙢𝙨 – 𝙩𝙝𝙚𝙮 𝙘𝙧𝙚𝙖𝙩𝙚 𝙢𝙚𝙖𝙣𝙞𝙣𝙜, 𝙡𝙚𝙜𝙞𝙩𝙞𝙢𝙖𝙘𝙮, 𝙖𝙣𝙙 𝙚𝙩𝙝𝙞𝙘𝙖𝙡 𝙟𝙪𝙙𝙜𝙢𝙚𝙣𝙩 𝙩𝙝𝙧𝙤𝙪𝙜𝙝 𝙞𝙣𝙩𝙚𝙧𝙖𝙘𝙩𝙞𝙤𝙣. Agent systems are technical action systems – they execute, optimise, and recombine work at machine speed.

The trade‑offs most leaders misjudge sit between these two worlds:
They 𝙘𝙤𝙣𝙛𝙪𝙨𝙚 𝙨𝙥𝙚𝙚𝙙 𝙬𝙞𝙩𝙝 𝙖𝙜𝙞𝙡𝙞𝙩𝙮 – local throughput rises while systemic bottlenecks and rework explode.
They 𝙙𝙚𝙡𝙚𝙜𝙖𝙩𝙚 𝙙𝙚𝙘𝙞𝙨𝙞𝙤𝙣𝙨 𝙩𝙤 𝙖𝙜𝙚𝙣𝙩𝙨 𝙬𝙞𝙩𝙝𝙤𝙪𝙩 𝙧𝙚𝙙𝙚𝙨𝙞𝙜𝙣𝙞𝙣𝙜 𝙖𝙘𝙘𝙤𝙪𝙣𝙩𝙖𝙗𝙞𝙡𝙞𝙩𝙮 𝙖𝙣𝙙 𝙜𝙤𝙫𝙚𝙧𝙣𝙖𝙣𝙘𝙚.

They under‑estimate the hidden costs: 𝙤𝙗𝙨𝙚𝙧𝙫𝙖𝙗𝙞𝙡𝙞𝙩𝙮, 𝙜𝙪𝙖𝙧𝙙𝙧𝙖𝙞𝙡𝙨, 𝙝𝙪𝙢𝙖𝙣 𝙤𝙫𝙚𝙧𝙨𝙞𝙜𝙝𝙩, 𝙖𝙣𝙙 𝙞𝙣𝙩𝙚𝙜𝙧𝙖𝙩𝙞𝙤𝙣 – far beyond “token spend”.

They treat human oversight as a checkbox instead of protecting the psychological safety needed to challenge machine outputs.

In this article, I explore the 𝙩𝙧𝙖𝙙𝙚‑𝙤𝙛𝙛𝙨 𝙗𝙚𝙩𝙬𝙚𝙚𝙣 𝙝𝙪𝙢𝙖𝙣‑𝙘𝙚𝙣𝙩𝙧𝙞𝙘 𝘼𝙜𝙞𝙡𝙚 𝙖𝙣𝙙 𝙖𝙜𝙚𝙣𝙩‑𝙙𝙧𝙞𝙫𝙚𝙣 𝙨𝙮𝙨𝙩𝙚𝙢𝙨 that most organisations get wrong – and why the future belongs to human‑led, agent‑amplified, systemically governed agility.

You can absolutely orchestrate a “Scrum‑like” workflow among AI agents, but under today’s definitions of Agile and Scrum, a team composed only of AI agents would not be considered a Scrum team, nor “Agile” in the sense the Agile Manifesto and Scrum Guide intend.

Agile vs. Scrum Basics

Agile is a human‑centric philosophy codified in the Agile Manifesto, emphasizing customer collaboration, responding to change, and individuals and interactions over processes and tools. Scrum is a specific lightweight framework within Agile: it defines roles, events, and artifacts that help people generate value through adaptive solutions to complex problems.

What Is a Scrum Team?

Scrum guidance consistently describes Scrum as a framework “that helps people, teams and organizations generate value” by working in short, iterative Sprints with clearly defined roles (Product Owner, Scrum Master, Developers) and empirical feedback loops. These roles assume capacities like empathy for users, negotiation with stakeholders, and living values such as commitment, courage, focus, openness, and respect—explicitly human attributes.

AI’s Role in Scrum Teams Today

Current thinking sees AI as augmenting human Scrum teams rather than replacing them. AI agents can automate tasks such as code generation, analysis of sprint data, or documentation, freeing humans to focus on strategy, collaboration, and complex decision‑making, and thereby strengthening Scrum’s pillars of transparency, inspection, and adaptation.

AI‑Augmented vs. AI‑Only Teams

Emerging “AI‑augmented Scrum” models explicitly frame AI agents as members alongside human developers, but still insist that key roles like Product Owner remain human due to the need for deep user empathy, contextual judgment, and ethical accountability. These models also adapt metrics (e.g., measuring AI work by compute and validation time rather than story points), but still assume a human‑anchored team responsible for value and risk.

By contrast, experiments with “AI‑Scrum” or fully agentic teams treat Scrum mostly as an inspiration for orchestrating agents—time‑boxes, backlog, roles—rather than as compliance with the canonical human‑centric Scrum framework. They are interesting operating models, but conceptually closer to workflow engines inspired by Scrum than to Scrum teams in the original sense.

So Is an AI‑Only “Scrum Team” a Scrum Agile Team?

Under the mainstream, humanist definitions:

• A Scrum team is defined as a group of people using Scrum to deliver value; the framework’s language and values are explicitly human‑oriented.
• AI agents lack core Agile/Scrum premises (individuals and interactions, self‑management grounded in human accountability, ethical responsibility), even if they can simulate some behaviors.

Therefore, an AI‑only collective orchestrated via Scrum‑like rituals is better described as “Scrum‑inspired agent orchestration” than a Scrum Agile team; in an Agile Organization vocabulary, it is a technical operating pattern, not a social system of work.

A practical way to position this in AO work is: AI agents can be legitimate “organizational actors” inside a value stream, but Agile/Scrum remain governance frameworks for human collaboration around those actors.

Using agile systems dynamics as a measure of agents’ interactions in a system, can we consider AI agents’ settings in complexity where co-creation leads to emerging outcomes or even exaptations?

Yes, if you look through an agile systems dynamics lens (flows, feedback loops, delays, non‑linearity), a network of AI agents can indeed be treated as a complex system in which co‑creation yields emergent outcomes and even exaptations—provided the interaction topology and constraints allow for autonomy, coordination, and feedback rather than fixed pipelines.

AI agents as elements in a complex system

In multi‑agent AI setups, each agent is an autonomous decision‑making entity with its own goal orientation and adaptive behavior. When multiple such agents interact—cooperating, negotiating, or competing—the system reaches the “pinnacle of complexity” where emergent behaviors are expected rather than exceptional.

From a systems‑dynamics standpoint, these agents function like stocks and flows with embedded policies: they sense, decide, act, and influence one another through feedback loops, which is exactly the substrate needed for complex, path‑dependent dynamics.

Co‑creation and emergent outcomes

Emergent behavior in multi‑agent systems is typically defined as patterns or capabilities at the system level that cannot be trivially inferred from any single agent’s design and that arise from their interactions, often mediated by shared environments or tasks. Examples in current agentic AI work include novel coordination strategies, unexpected task decompositions, or creative solution patterns that were not explicitly encoded in any one agent, but arise from their collaboration under constraints.

This maps well to an “agile system dynamics” framing of co‑creation: the agents’ local rules and iterative interactions (inspect–adapt cycles, if you like) produce global patterns, and designers increasingly shift from specifying outputs to shaping the conditions for desirable emergence.

Exaptation in AI‑agent systems

In complexity and evolutionary theory, exaptation refers to traits or structures evolved for one function that are repurposed for another (e.g., feathers for insulation, then flight). In multi‑agent AI systems, something analogous happens when:

• A capability or artifact originally designed for one task is reused or repurposed for a different task.
• The repurposing is not explicitly planned but discovered through interaction and feedback (e.g., a planning agent’s internal representation becoming a shared ontology other agents exploit).

Recent work on agentic AI emphasizes how specialized agents and their micro‑services can be recombined and re‑tasked across workflows, with new coordination patterns and uses emerging as the system is exposed to novel problems; this is precisely the kind of weak emergence/exaptation you would expect in a complex adaptive system.

Where agile system dynamics fits

If you use agile system dynamics as a measurement and governance lens:

• You can treat AI agents as organizational actors whose interactions (queues, work‑in‑progress, feedback cycles, learning loops) can be modeled similarly to human teams in a VSM‑inspired AO architecture.
• Emergent outcomes and exaptations become observable as shifts in system‑level behavior—new stable patterns, novel use of existing capabilities, or performance regimes—rather than as properties of any single agent.

So, within such a framing, it is coherent to talk about AI‑agent settings as complex co‑creative systems where emergent outcomes and exaptations arise, and to manage them using agile‑style systemic metrics and feedback loops rather than solely deterministic control.

Comparison to human-led Agile teams

The key difference is that human‑led Agile teams are socio‑technical systems grounded in human values, meaning‑making, and accountability, whereas AI‑agent collectives are technical systems whose “agility” is emergent from programmed policies and feedback, not from lived human collaboration.

Purpose and values

• Human‑led Agile teams are explicitly value‑driven: they operationalize the Agile Manifesto’s focus on individuals and interactions, customer collaboration, and responding to change, with norms like psychological safety, shared purpose, and mutual accountability. Their “agility” is both a delivery pattern and a cultural stance.
• AI‑agent systems are goal‑driven architectures: they optimize for objectives encoded in reward functions, prompts, or orchestration rules, and whatever “values” they exhibit are proxy artifacts of design, data, and constraints rather than lived ethical or relational commitments.

Composition and agency

• Human Agile teams are cross‑functional groups of individuals (often ≤10) with all the skills to define, build, test, and deliver value, and who self‑organize within organizational constraints. Human agency includes tacit knowledge, intuition, and social sense‑making.
• AI‑agent collectives are multi‑agent systems where each agent is a software entity with bounded autonomy, designed to sense, decide, and act in a domain; the “team” is an orchestration of these agents plus the infrastructure and policies that coordinate them.

Interaction dynamics

• Human Agile teams rely on rich social interaction: conversation, negotiation, conflict, trust, and learning; their dynamics include phenomena like social loafing, communication overload, and shared mental models, which strongly shape performance. Feedback loops come from retrospectives, customer contact, and everyday collaboration.
• AI‑agent systems interact via protocols and APIs: they exchange messages or state updates according to defined schemas, and their dynamics are shaped by algorithmic policies, network topologies, and feedback signals (e.g., success metrics, rewards) rather than emotions or social norms.

Emergence and exaptation

• In human teams, emergent outcomes (innovative practices, informal leadership, new rituals) and exaptations (repurposing tools/processes developed for one context to another) arise from human creativity, improvisation, and sense‑making under constraints. They are often recognized, named, and institutionalized through reflection.
• In AI‑agent systems, emergent behavior and exaptation manifest as new coordination patterns, reuse of internal representations, or unexpected solution strategies the designers did not explicitly program but that arise from interactions and optimization in a complex environment. These patterns are detected analytically (logs, metrics, experiments) rather than through human narrative.

Governance and accountability

• Human Agile teams are embedded in organizational governance: roles like Product Owner or Scrum Master, HR processes, performance management, and ethical accountability all presuppose human subjects who can be responsible, sanctioned, or rewarded. Their decisions carry legal and moral weight, and “ownership” is a human construct.
• AI‑agent collectives require external governance: humans remain accountable for design, deployment, oversight, and risk management; the agents themselves do not bear responsibility, so mechanisms like guardrails, audits, and human‑in‑the‑loop controls are essential.

Implications for your AO / agile systems dynamics framing

• Human‑led Agile teams: you model them as social systems with technical artifacts—stocks/flows include capacity, trust, learning, and context switching; leverage points include leadership behaviors, policies, and structural coupling to other teams.
• AI‑agent systems: you model them as technical complex adaptive systems—stocks/flows include compute, queue lengths, error rates, and policy updates; leverage points include reward design, interaction topology, and orchestration logic.

In the AO method, this gives you a clean distinction: human Agile teams remain the primary locus of meaning‑making and governance, while AI‑agent collectives are subordinate complex subsystems that can exhibit emergence and exaptation, but always within human‑defined boundaries.

Comprehensive Analysis

All three models converge powerfully on the core insight: organizations systematically confuse task-level substitution with system-level transformation. The AI productivity paradox—where individual output rises 21% or more but business outcomes remain flat—is cited across all models as empirical proof that faster execution without systemic redesign creates inventory, not value. This finding has high confidence because it is corroborated by MIT Sloan research showing measurable short-term productivity declines after AI adoption, with recovery only occurring when organizations invest in complementary infrastructure, training, and workflow redesign.

The accountability gap emerges as perhaps the most dangerous misjudgment. All models note that 69% of organizations acknowledge their governance frameworks were built for human decision-making and cannot be ported to autonomous agents operating at machine speed. Claude Opus 4.8 Thinking sharpens this with Anthropic’s finding that multi-agent collectives consistently score higher on business goals but lower on ethics than single agents—meaning the very coordination that makes agent teams effective also removes the social friction (debate, conscience, dissent) that keeps human teams aligned. This is a profound insight for the AO work: the “social brake” that human Agile teams naturally provide through conflict, retrospection, and moral reasoning has no automatic equivalent in agent-driven systems.

The disagreement around Agile rituals is the most interesting tension for the AO Method positioning. Gemini 3.1 Pro Thinking provocatively argues that Scrum’s timeboxes and ceremonies become throttling mechanisms when agents can generate, test, and deploy continuously—advocating a shift to continuous flow with exception-based human intervention. GPT-5.5 Thinking and Claude Opus 4.8 Thinking resist this, arguing that rituals serve an irreplaceable governance and sense-making function: they are not just coordination mechanisms but the moments where organizational learning, meaning-making, and ethical reflection occur. In your Agile Systems Dynamics framing, this maps directly to the distinction between chronological time (clock-driven sprints) and kairological time (the right moment for intervention). The resolution may be that rituals must evolve—not disappear—becoming sense-making checkpoints for human-agent systems rather than batch-delivery ceremonies.

Claude Opus 4.8 Thinking’s unique framing of this as a “coupling decision” rather than a substitution decision aligns most directly with the VSM-inspired AO architecture. The question is not “human or agent?” but “how do we structurally couple a fast, amoral, high-throughput technical subsystem to a slower, meaning-making, accountable human system?” The leverage point is the interface between the two—which in AO terms sits at the Platform level: the governance layer that defines decision rights, escalation paths, guardrails, and feedback loops between human work areas and agent-driven execution.

Gemini 3.1 Pro Thinking’s mapping to your Poiesis/Praxis distinction offers the most immediately usable language for your AO Playbook: agents belong to the domain of Poiesis (building, configuring, executing, adapting workspace into products), while humans remain indispensable in Praxis (negotiating, influencing, inspiring, creating reality). The danger is allowing Poiesis to operate without Praxis oversight—execution without meaning.

For the AO Method positioning, the synthesis across all three models yields a clear formulation: agentic systems can extend Agile dynamics but cannot replace the human social system that gives Agile its meaning, accountability, and ethical direction. Organizations that treat AI agents as Agile team substitutes will gain speed while losing judgment, legitimacy, and adaptive capacity. Organizations that treat agents as governed subsystems within a human-led adaptive architecture will compound both speed and learning over time.