AI Team Programs • AI-DLC and Kiro

AI-DLC and Kiro Team Enablement

For software delivery teams adopting AWS's AI-Driven Development Life Cycle with Kiro as their coding agent, including teams moving from Amazon Q Developer to Kiro. The whole team learns the method together, then developers go deep on Kiro.

4
Training Days
28
Training Hours
+3
Days with Add-on

Schedule: 4 consecutive days, or two 2-day blocks a week or more apart. 7 days with the optional agent course.

AWSAWS AI-DLC
Kiro IDE and Kiro CLI
Model Context ProtocolMCP
PythonStrands Agents (add-on)

The Path

Two catalog courses taught in this order, plus an optional third. Each title links to the full course outline.

Step1

The whole team learns AI-DLC's phases, approval gates, and mob sessions. Then everyone runs the open-source AI-DLC Workflows in Kiro.

Step2

Spec-Driven Agentic Coding with Kiro

14 training hours · 2 days

Developers build features from Kiro specs: EARS requirements, a design, and a task plan. The course also covers steering, hooks, powers, Kiro CLI in CI, cloud sessions, and moving from Amazon Q Developer.

Tailoring Options

We adjust the path to your rollout, your team's roles, and the codebases you work in.

Mixed-role teams

Product owners, QA engineers, and managers can attend the AI-DLC course only, or take the one-day AI-DLC and Spec-Driven Development for Product Owners and Business Analysts course instead. The Kiro course is hands-on and aimed at the developers who drive the agent.

Moving from Amazon Q Developer

Amazon Q Developer IDE plugins and paid subscriptions reach end of support on April 30, 2027. The Kiro course has a migration module, and we weight it and the admin topics to match your rollout plan.

Other coding agents

AI-DLC Workflows also run in Claude Code, GitHub Copilot, Cursor, and Codex. If part of the team uses one of those, we show the workflow there as well.

Building agents on AWS

Teams that will build their own agents can add the 3-day Strands Agents and AgentCore course. It needs Python and an AWS account with Bedrock and AgentCore access.

Greenfield or brownfield: we use examples from your domain, and one of your repositories where you can share it.

Who Should Attend

Delivery teams that already use, or are about to license, Kiro and want a shared method with clear roles, human approval gates, and an audit trail.

  • Developers and tech leads
    Who will drive Kiro day to day. Git, the command line, and a Kiro account are needed.
  • Architects and QA engineers
    Who review requirements, designs, and approval gates.
  • Product owners and managers
    Who take part in AI-DLC elaboration and sign-off. No deep coding skills needed.
  • Platform and DevEx teams
    Who administer Kiro, credits, and models for the organization.

Request This Program

We'll respond within 1 business day