The conversation around AI in the software development lifecycle has matured. The question is no longer whether AI belongs in engineering workflows. The harder question is how teams use it in production without creating new problems around governance, quality, security, and accountability.
That is the backdrop for AI in SDLC: Executive Panel & Hands-on Workshop with Kiro and Codex, an upcoming AWS Connected Community event scheduled for July 1, 2026, at AWS in Seattle. The session combines an executive panel with a hands-on workshop focused on Kiro and OpenAI Codex, giving engineering leaders and builders a place to discuss what happens after the AI demo.
This article covers the July 1, 2026, Kiro and Codex workshop specifically. AWS has hosted other AI in SDLC events with different tool combinations and speaker lineups, so the details here should not be blended with those of those separate sessions.
About the July 1 AI in SDLC Workshop
The July 1, 2026, event is framed around a practical shift in software engineering. AI coding tools are no longer experimental assistants. They are becoming part of planning, implementation, testing, documentation, and deployment workflows.
The official event description centers on AI-driven development and the software development lifecycle. Shikhar Kwatra has also described the discussion as focusing on what is working beyond demonstrations, how organizations are moving from experimentation into production, how developer velocity can improve without sacrificing governance, and how engineering roles continue to evolve as AI becomes part of everyday software delivery.
The hands-on portion matters because it turns the event from a panel about AI into a working session around real tools. Attendees are encouraged to bring laptops and hard questions, suggesting a room built for practitioners rather than passive observers.
That orientation fits the moment. Many organizations have already tested AI coding assistants. Fewer have answered the operational questions that follow: Who reviews AI-generated work? How is quality measured? What governance belongs in the workflow? How do teams decide which parts of the software lifecycle should remain human-led?
Why It Matters Now
Software teams are entering a more serious phase of AI adoption.
The first phase rewarded experimentation. Teams tested assistants, ran pilots, and measured whether developers could move faster. The next phase is less forgiving. It requires engineering organizations to turn AI into repeatable systems capable of operating under production constraints.
AWS has outlined an AI-Driven Development Life Cycle methodology in which AI participates across planning, construction, and operations while maintaining human oversight. Kiro represents AWS's spec-driven approach to agentic development workflows. OpenAI Codex represents another path toward agentic coding across terminal, IDE, and cloud environments.
Putting those tools into the same workshop creates a useful comparison for engineering leaders. The strategic question is not which product delivers the most impressive demonstration. It is how each approach changes the work of planning, reviewing, securing, and shipping software.
For founders and technical leaders, that distinction matters. Speed alone is not enough if it introduces risks that teams cannot see until later. The real advantage comes from combining faster execution with better judgment about what should be automated, what should be reviewed, and where accountability belongs.
The Panel Lineup
The confirmed July 1 speaker lineup includes Shikhar Kwatra, Chad Neal, Luke Stevens, Abhisheikh Lahoti, and Josh Browder. Shikhar Kwatra brings the OpenAI perspective and prior AWS experience, creating a bridge between Codex, enterprise deployment, and AWS-native engineering environments.
Chad Neal brings an AWS cloud architecture perspective on how AI-assisted development fits into production delivery systems rather than isolated experiments.
Luke Stevens, affiliated with Jellyfish, contributes an engineering measurement perspective. That lens is increasingly important because teams adopting AI need to evaluate impact beyond anecdotal productivity gains.
Abhisheikh Lahoti adds an AWS ecosystem and platform perspective, including how partner and marketplace dynamics may shape AI-native software delivery.
Josh Browder, founder and CEO of DoNotPay, contributes the perspective of a product builder operating in a highly scrutinized AI category. That viewpoint is valuable because AI governance stops being theoretical when software touches legal, consumer, or regulated workflows.
The mix is useful because it does not represent a single-vendor narrative. It brings together cloud architecture, agentic coding, engineering intelligence, partner ecosystems, and AI-native product development.
What Kiro and Codex Put Into the Room
Kiro and Codex are both part of the broader move from AI-assisted coding toward AI-native software development, but they approach the problem from different directions.
Kiro is associated with spec-driven development, where requirements, design, acceptance criteria, and implementation planning become structured parts of the AI workflow. That approach matters because many software failures begin before code is written, when teams misunderstand requirements or lack design clarity.
OpenAI Codex emphasizes agentic coding across developer environments, including command-line and IDE workflows. Its relevance for enterprise teams extends beyond code generation to delegating bounded engineering tasks while preserving review, sandboxing, and approval gates.
The workshop format makes the comparison more useful because it moves beyond product positioning. Attendees can ask how these tools fit into existing repositories, team rituals, security models, and release processes.
Those questions are where AI adoption becomes operational. The tools matter, but the operating model around them may matter even more.
Why Seattle and AWS Connected Community Matter
Seattle remains one of the world's strongest centers for cloud infrastructure, enterprise software, developer tooling, and AI talent. Hosting this discussion at AWS places it within an ecosystem where many companies already build and operate cloud-native software at meaningful scale.
AWS Connected Community is also a fitting host because its programming is designed for builders and operators navigating real technology transitions. For this event, that means the discussion can stay focused on practical implementation rather than broad predictions about AI's future.
AWS Connected Community is the event host, and AWS Seattle provides the venue. The event information does not identify OpenAI, Jellyfish, DoNotPay, iSpot, or other organizations as sponsors. Those organizations are represented through speaker affiliations rather than event sponsorship.
That distinction matters because multiple AI in SDLC events share similar names. Keeping the July 1 Kiro and Codex workshop separate from other AWS sessions preserves the accuracy of the discussion.
What Engineering Leaders Should Watch
The event is worth watching because it sits at the point where AI coding stops being a novelty and becomes an organizational design question. Engineering leaders should pay close attention to how the panel frames governance. The strongest AI development workflows will likely be the ones that make review, traceability, security, and human judgment easier to apply, not harder.
They should also pay attention to measurement. If AI changes how software is planned and built, teams need better ways to determine whether quality, throughput, maintainability, and customer outcomes are improving together.
Finally, they should watch how builders talk about roles. AI does not eliminate the need for product judgment, architecture, code review, incident response, or accountability. It changes where those responsibilities appear within the workflow.
That is why the July 1 workshop is more than a tool demonstration. It signals that the next phase of AI in software development will be judged by execution discipline rather than enthusiasm.
For founders, CTOs, engineering managers, and product leaders responsible for production software, that is the conversation worth having before the next development cycle begins.
Frequently Asked Questions
What is the AI in SDLC: Executive Panel & Hands-on Workshop with Kiro and Codex?
It is an AWS Connected Community event scheduled for July 1 at AWS in Seattle, combining an executive panel with a hands-on workshop focused on AI in the software development lifecycle using Kiro and OpenAI Codex.
Who are the confirmed speakers for the July 1 event?
The lineup includes Shikhar Kwatra, Chad Neal, Luke Stevens, Abhisheikh Lahoti, and Josh Browder.
Who is hosting the event?
The event is hosted by AWS Connected Community through the AWS Experience platform.
Where will the event take place?
The event is scheduled to take place at AWS in Seattle.
Why does this event matter for engineering leaders?
The workshop focuses on moving AI from experimentation into production while addressing governance, software quality, engineering workflows, and the changing role of human judgment across the software development lifecycle.