AIToday
Top Companies' AI MovesLarge Language ModelsAI Coding AssistantsTop Companies AIPublished: Aug 5, 2026, 06:31 JST3 min read

AWS defines AI-DLC: a new software development methodology centered on AI collaboration

AWS defines AI-DLC: a new software development methodology centered on AI collaboration

Key takeaway

  • AWS has introduced the AI-DLC (AI-driven development lifecycle), a new software development methodology that places AI models at the center of every phase—from planning and design through coding, testing, and deployment—rather than using them as auxiliary tools.

  • The framework treats AI as an active collaborator that continuously maintains project context, asks clarifying questions, and autonomously executes tasks while humans retain oversight and approval authority.

  • This represents a fundamental shift from human-centric methodologies like Agile, allowing organizations to streamline team structure and reduce handoffs by collapsing traditional phase boundaries into continuous, non-linear workflows.

3 Key Points

  1. What happened

    AWS's Raja SP coined the term "AI-driven development lifecycle" (AI-DLC) in 2025 and published a whitepaper outlining ten principles and a framework that treats large-language models as active collaborators throughout every step of software development, rather than as isolated code-generation tools.

  2. Why it matters

    Unlike previous methodologies such as Agile and Scrum—which were built around human coordination—the AI-DLC reimagines the entire development process around machine-human collaboration. AI agents ask clarifying questions, maintain project context, propose designs, generate and validate code, and manage deployment autonomously while humans retain supervisory approval. This potentially allows smaller, more integrated teams to handle the complexity of enterprise systems that once required separate specialist teams.

  3. What to watch

    The framework is standardized around AWS tools like Kiro and Amazon Q Developer, but can also integrate with other agentic platforms such as IBM Bob and Claude Code. Organizations are encouraged to adopt the rituals and embed AI-DLC into their own orchestration tools gradually, minimizing disruptive overhauls.

Ask the AI about this article →

Context & Analysis

The AI-DLC emerges from the recognition that AI fundamentally changes the constraints and possibilities of software development. Earlier methodologies—from Waterfall to Agile—were designed to coordinate human effort within human cognitive and organizational limits. By contrast, the AI-DLC asks what development would look like if AI had always existed as a core participant. The ten principles Raja SP outlines reflect this inversion: rather than bolting AI onto existing workflows, the methodology centralizes design disciplines (Domain-driven design, Behavior-driven development, Test-driven development), continuously preserves context across the entire project lifecycle, and automates handoffs between traditional phases.

The framework's three phases—inception, construction, and operations—blur the boundaries that separate planning from design from implementation. In the inception phase, mob elaboration (a collaborative ritual between human teams and AI systems) translates business intents into user stories and units of work. Steering files, stored as markdown documents, act as persistent constraints and rules that AI agents follow throughout all phases. During construction, AI agents can propose architectures, schemas, and code autonomously, with humans validating and refining. In operations, AI extends beyond deployment to treat production systems as continuous feedback loops. This structure suggests that organizations adopting AI-DLC may reduce the need for handoffs between specialist teams—since AI can maintain context across disciplines—and compress the traditional feedback loops that plagued earlier waterfall and even Agile approaches.

FAQ

Who created the AI-DLC and when?
AWS's Raja SP coined the term and described the methodology in his "AI-Driven Development Lifecycle (AI-DLC) Method Definition" whitepaper in 2025.
What are the main phases of the AI-DLC framework?
The framework has three phases: inception (where intents are captured and translated into units of work via mob elaboration), construction (where humans and AI collaboratively write, test, and deploy code), and operations (where AI manages deployment, automates infrastructure, and monitors the live system).
How does the AI-DLC differ from simply adding AI to existing Agile workflows?
The AI-DLC is a fundamental reimagining rather than an augmentation of existing methodologies. Instead of treating AI as a mere productivity tool, it centers the entire development process around machine-human collaboration, with AI taking on a more autonomous role and humans moving into a supervisory position. Previous approaches that simply added AI to Agile were described as producing "a faster horse," whereas the AI-DLC represents a core evolution.
Top Companies AIRead Original Article

Get the latest Top Companies' AI Moves news every morning

For example, today's edition would include:

  • GE Vernova's New MV-UPS Could Triple Revenue Per GigawattTop Companies AI · 14h ago
  • Lam breaks ground on Oregon lab for AI chip R&DTop Companies AI · 14h ago
  • Ole Miss Study: AI Ads Fail When Consumers Feel TrickedTop Companies AI · 14h ago

AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.

Free · takes 30 seconds · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. Q&As are published on this page for other readers too.

Related Articles

Next articleNTT Docomo targets full AI automation of marketing by 2027