Peter Pedross, CEO & Founder, PEDCO – SAFe Fellow

Agentic Engineering is not simply about introducing autonomous agents into software development. It is about creating an engineering organization in which humans and autonomous systems operate within the same architectural principles, governance structures and organizational knowledge. This requires a new operating model. A Lean Quality Management System provides exactly this foundation by becoming the shared operational environment in which engineering decisions are made, knowledge evolves and continuous improvement becomes part of everyday work.

Bringing Everything Together

Throughout this series, we have gradually explored the individual building blocks of Agentic Engineering. We discussed why engineering productivity alone will no longer differentiate successful organizations. We examined why architecture becomes increasingly important, why documentation evolves into operational context, why governance must become executable and why Context Engineering ultimately matters more than Prompt Engineering. Individually, each of these topics addresses a specific challenge facing modern engineering organizations. Together, however, they describe something much larger. They describe a fundamentally new operating model. Rather than discussing individual concepts, the remainder of this article walks through the different layers of this operating model.

Every major engineering revolution has eventually transformed the way organizations work. Object-oriented programming changed how software was designed. Agile changed how teams planned and collaborated. DevOps transformed software delivery by integrating development and operations into a continuous flow of value.

Agentic Engineering introduces another transition of similar significance.
For the first time, engineering organizations are no longer composed exclusively of people. Increasingly, they consist of people and autonomous systems working toward the same objectives and contributing to the same engineering outcomes. At first glance, this may appear to be a relatively small distinction. In practice, however, it changes almost everything. Traditional operating models were designed for human collaboration. They assumed that engineers would interpret documentation, understand context, communicate intent and resolve ambiguity through experience and discussion.

Autonomous agents operate differently. 
They require explicit responsibilities, explicit context and explicit objectives. They require clearly defined constraints and, perhaps more importantly than anything else, they require consistency. An operating model designed exclusively around human interaction therefore becomes increasingly insufficient as autonomous systems assume more responsibility within engineering organizations.

What emerges instead is the need for an operating model that enables humans and autonomous systems to collaborate effectively while sharing the same engineering knowledge, architectural principles and governance structures. Although frameworks like SAFe were originally developed to improve collaboration between people, many already contain exactly the artifacts and terms which autonomous systems require in order to operate effectively. e.g. Solution Intent, Architecture Runway, Architecture Decision Records, DevOps, roles with RACI, Decision Boundaries, Guardrails. Individually, none of these concepts is particularly new. Collectively, however, they become something much more significant. Together they establish a shared engineering context that supports people, autonomous agents and, perhaps most importantly, future engineering decisions that have not yet been made. Viewed from this perspective, the purpose of an operating model begins to evolve. It no longer exists solely to coordinate human activities. Increasingly, it exists to coordinate decision-making across an engineering organization in which humans and autonomous systems continuously contribute to the delivery of value. This observation closely mirrors our own experience.

At first glance, this may appear to be a relatively small distinction. In practice, however, it changes almost everything.

From Human Collaboration to Shared Decision-Making

Traditional operating models were designed around people. Roles were assigned to individuals, responsibilities were distributed across teams, and engineering processes implicitly assumed that experienced engineers would interpret documentation, understand organizational context, resolve ambiguity and communicate intent through discussion, collaboration and accumulated experience. Much of the effectiveness of these operating models depended on knowledge that existed inside the organization rather than being explicitly documented.

Autonomous agents operate fundamentally differently. They cannot rely on intuition, institutional memory or informal conversations to understand what is expected of them. Instead, they require explicit objectives, clearly defined responsibilities, well-understood constraints and a consistent engineering context within which decisions can be made. Above all, they require consistency. Every decision should be based on the same architectural principles, governance policies and organizational objectives, regardless of which autonomous agent performs the work.

As a result, an operating model designed exclusively around human interaction becomes increasingly insufficient. Organizations need an operating model that enables humans and autonomous systems to collaborate within the same engineering environment, sharing not only engineering knowledge, but also architectural principles, governance structures and organizational intent.

The purpose of an operating model therefore begins to evolve. Rather than coordinating human activities alone, it increasingly becomes the framework that coordinates engineering decisions across an organization where people and autonomous systems continuously work together to create value. In this environment, consistency, transparency and shared context become just as important as collaboration itself, providing the foundation upon which both humans and autonomous agents can make high-quality engineering decisions.

The Agentic Engineering Operating Model

This realization fundamentally changes how we should think about an operating model. In the pre-Agentic world, operating models primarily described organizational structures, reporting relationships and the coordination of work between people. In the age of Agentic Engineering, however, an operating model evolves into something much more comprehensive. It increasingly describes the engineering environment in which both humans and autonomous systems make decisions, collaborate and continuously create value.

Every engineering decision begins with purpose. Business strategy, portfolio priorities, customer needs and organizational objectives continue to provide the direction for engineering work. Autonomous systems should never optimize isolated implementation tasks without understanding the broader outcomes they are intended to achieve. Strategy therefore remains fundamentally a human responsibility while becoming increasingly transparent and accessible to autonomous systems.

Between strategic intent and engineering execution lies what we believe becomes the most valuable asset of every engineering organization: its shared engineering context.

As mentioned before in this series, we have repeatedly encountered the same engineering artifacts. Solution Intent captures engineering intent rather than simply documenting requirements. The Architecture Runway provides long-term technical direction instead of isolated design decisions. Architecture Decision Records preserve engineering reasoning that would otherwise disappear over time. Process models describe how the organization works. Governance defines decision boundaries. Working agreements establish expected engineering behaviour. Quality standards define acceptable outcomes, while DevOps pipelines transform engineering intent into executable delivery processes.

Individually, none of these concepts is particularly new. Collectively, however, they become something much more significant. Together they establish the shared engineering context within which both humans and autonomous systems operate. Rather than serving as static documentation, they become the operational environment that continuously guides engineering decisions.

From this perspective, autonomous agents should not simply have access to organizational knowledge. They should operate within it.

Humans and Autonomous Agents

The engineering organization itself also begins to evolve. Product managers, architects, engineers, quality specialists and security experts continue to play essential roles, but they are increasingly joined by autonomous design agents, implementation agents, testing agents and operational agents. Each participant contributes different capabilities, yet all operate according to the same architectural principles, governance model and organizational objectives.

Autonomous agents do not replace engineers.
They become additional engineering participants contributing to the same value stream.

Engineering delivery itself changes surprisingly little. Organizations still discover opportunities, refine requirements, design solutions, implement software, validate quality, deploy systems and continuously improve their products. What changes is how these activities are performed:

Autonomous systems increasingly participate throughout the entire engineering lifecycle. Documentation is no longer created after implementation has finished. Evidence emerges continuously. Architecture validation becomes part of development itself. Compliance is no longer reconstructed after delivery but becomes an inherent characteristic of everyday engineering work.

 

 

This insight fundamentally changes how organizations should approach Agentic Engineering. The objective is not to optimize individual agents. The objective is to continuously improve the engineering environment in which those agents operate.

Continuous Delivery, Continuous Learning

One observation repeatedly emerged throughout our own engineering work. We refined our Solution Intent, strengthened architectural guidance, clarified responsibilities, improved documentation and created stronger integration between architecture, Lean Quality Management, governance and DevOps. What surprised us was how immediately every improvement benefited every autonomous participant. The engineering system itself became smarter—not because the underlying language models had changed, but because the organization had become better at providing context. Every refinement to the engineering environment improved the quality, consistency and explainability of engineering decisions across the entire organization. Interestingly, the engineering lifecycle itself changes remarkably little.

  • What changes is not the lifecycle.
  • What changes is participation.

Autonomous systems increasingly contribute throughout every stage of engineering. Documentation is no longer produced after implementation has finished. Evidence emerges continuously while engineering work is taking place. Architecture validation becomes part of implementation itself. Compliance is no longer reconstructed after delivery but develops naturally as an integral part of engineering. Continuous feedback improves not only the capabilities of engineers but also those of autonomous systems, allowing the engineering organization itself to learn.

Ultimately, organizations do not invest in Agentic Engineering simply to deploy autonomous agents or adopt the latest AI technologies. They invest because they expect better outcomes.

This insight fundamentally changes how organizations should approach Agentic Engineering. The objective is no longer to optimize individual agents. The objective is to continuously improve the engineering environment in which those agents operate. As the engineering system itself becomes more explicit, structured and connected, both humans and autonomous systems benefit simultaneously. In the age of Agentic Engineering, the engineering system—not the individual AI agent—ultimately becomes the organization’s most valuable asset.

The objective is to make better engineering decisions, deliver higher product quality, achieve continuous adherence to architectural and organizational principles, accelerate delivery, and strengthen architectural integrity. At the same time, organizations improve their ability to learn, create more valuable products, and ultimately deliver greater value to their customers. Agentic Engineering is therefore not about replacing engineers with AI, but about building engineering organizations that consistently produce better outcomes.

Lean Quality Management Becomes the Operating System

Perhaps the most significant consequence of Agentic Engineering is that Lean Quality Management assumes an entirely new role within modern engineering organizations. Seen from a pre-Agentic perspective, Quality Management Systems have been viewed primarily as repositories of documented processes, compliance requirements and audit evidence. Their purpose was to describe how engineering should be performed and to demonstrate, often retrospectively, that organizational and regulatory obligations had been fulfilled. In the age of autonomous engineering, however, this perspective becomes far too limited.

A Lean Quality Management System increasingly evolves into the operating system of the engineering organization itself. Rather than simply documenting how work should be performed, it provides the environment within which engineering decisions are made. It captures organizational knowledge, establishes architectural principles, defines governance, distributes responsibilities, connects engineering processes with DevOps and continuously generates objective evidence. Most importantly, it enables continuous learning by making organizational knowledge explicit, reusable and continuously available.

A Lean Quality Management System becomes the operating system of the engineering organization.

Viewed from this perspective, a Lean Quality Management System defines far more than processes. It defines how an engineering organization thinks, how it makes decisions, how it learns from experience and how it continuously improves. Humans operate within this environment, and autonomous agents operate within exactly the same environment. Both rely on the same architecture, the same governance, the same quality standards and the same organizational knowledge. This shared operating model ensures that engineering decisions remain consistent regardless of whether they are made by people or by autonomous systems.

This represents an important shift in perspective:

  • Lean Quality Management is no longer primarily about achieving compliance.
  • Compliance increasingly becomes a natural consequence of a well-designed engineering system rather than its primary objective. In this sense, compliance is no longer something you build separately—it emerges from the way the system is engineered.
  • The real purpose of a Lean Quality Management System is to provide the operational context within which every engineering participant—human or autonomous—can make high-quality decisions that remain aligned with the organization’s architecture, governance and business objectives.

One observation repeatedly emerged throughout our own engineering work. As autonomous agents became increasingly capable, we found ourselves investing progressively less effort in improving individual agents and considerably more effort in improving the engineering system itself. We refined our Solution Intent, strengthened architectural guidance, clarified responsibilities, improved documentation and further integrated architecture, Lean Quality Management, governance and DevOps into a coherent engineering environment. Every one of these improvements immediately benefited every autonomous participant.

The engineering system itself became smarter—not because the underlying language models had changed, but because the organization had become better at providing context.

This insight fundamentally changes how organizations should approach Agentic Engineering. The objective is no longer to optimize individual agents or continuously search for more capable AI models. The objective is to continuously improve the engineering system in which those agents operate. As the operating environment becomes more explicit, more connected and more consistent, every participant in the organization benefits simultaneously. In the age of Agentic Engineering, the true competitive advantage no longer lies in the intelligence of individual agents. It lies in the intelligence of the engineering system that guides them.

Applied SAFe as an Example

Applied SAFe provides a practical example of how a Lean Quality Management System can evolve into the operating model of an engineering organization. Originally developed for large engineering organizations based on the Scaled Agile Framework, its objective was never to support autonomous systems. Instead, it was designed to establish a common engineering language, align architecture with execution, integrate governance into everyday engineering work and enable continuous improvement without sacrificing agility. Applied SAFe is an interactive and ALM tool-agnostic framework of how to achieve business agility in a regulatory compliant way. Facilitated by customizable and tailorable descriptions with clearly defined roles, their interaction, and supporting artifacts, it enables a clear and common understanding for all participants. With mapping to existing organizational processes and regulatory standards, it ensures agility and compliance of activities as self-proving evidence.

Looking at Applied SAFe through the lens of Agentic Engineering reveals an interesting observation. Many of the engineering artifacts that were originally introduced to improve collaboration between people are exactly the artifacts autonomous systems require in order to operate effectively. Solution Intent, the Architecture Runway, Architecture Decision Records, governance, process models, working agreements, quality standards and DevOps pipelines no longer serve merely as documentation or process guidance. Together, they establish a shared engineering context that enables both humans and autonomous agents to reason about engineering decisions using the same architectural principles, organizational knowledge and governance model.

As a consequence of this evolution, Applied SAFe introduces Agentic Engineering as an optional capability. AI skills, agent hooks, execution rules, and related engineering artifacts can be added as an extension to the existing Lean Quality Management System, allowing organizations to adopt autonomous engineering incrementally while preserving their established governance model.

Agentic Engineering is not a new engineering methodology.
It is an extension of an already well-designed engineering operating model.

Perhaps this is one of the most surprising consequences of Agentic Engineering. It does not necessarily require entirely new engineering concepts. Instead, it gives many existing engineering practices a fundamentally new purpose. Artifacts that once supported collaboration between engineers evolve into the operational context that enables autonomous systems to participate in engineering work. Documentation becomes context. Process descriptions become executable engineering behavior. Organizational knowledge becomes continuously available as part of everyday decision-making.

Viewed from this perspective, Applied SAFe evolves beyond its original role as a Lean Quality Management System. It increasingly provides the shared engineering context within which people and AI-assisted engineering activities can operate consistently. Rather than serving primarily as documentation, its artifacts become operational assets that capture engineering intent, architectural direction, governance, quality expectations and organizational knowledge. The real value no longer lies in describing how an organization works. It lies in making engineering knowledge explicit, connected and continuously available so that both people and autonomous systems can contribute within the same trusted engineering environment while maintaining clear human accountability.

One of the more interesting observations is that many mature engineering frameworks already contain much of the context autonomous systems require. Artifacts such as Solution Intent, Architecture Runway, Architecture Decision Records, Working Agreements and DevOps pipelines were originally introduced to improve collaboration between people. Increasingly, they also provide the structured engineering context that enables AI-assisted engineering to operate consistently and transparently.

This observation also aligns closely with the direction in which the Scaled Agile Framework is evolving. AI-Native SAFe expands the role of AI throughout the software development lifecycle and strengthens collaboration between people and AI-enabled engineering teams. Rather than replacing human responsibility, it reinforces the importance of clear engineering context, decentralized decision-making and explicit governance. We believe the next logical step is to make this shared engineering context itself increasingly operational. Architecture, Solution Intent, Lean Quality Management, governance, process models and engineering knowledge together form the environment within which people lead, AI assists and engineering decisions remain transparent, explainable and continuously aligned with organizational intent.

People lead. AI assists. Engineering knowledge connects both.

One final capability now remains. If autonomous systems increasingly participate in engineering decisions, organizations must also continuously verify that these decisions remain aligned with architecture, governance and organizational intent.

Continuous Adherence.

Previous Chapter Next