Build & Test meets Deploy & Manage - experimentation loops plus runtime optimization for production agents.
AI Agentic Practice
Agent Development Lifecycle (ADLC)
Traditional software SDLC is not enough for AI agents. Gensten’s Agent Development Lifecycle (ADLC) is the new tech stack SDLC for agentic systems: use-case alignment and KPI definition, agent development with MCP integrations and OpenTelemetry, eval-driven release into a governed catalog, production rollout with multi-agent orchestration, continuous KPI optimization, and real-time monitoring with regulatory alignment. Build & Test and Deploy & Manage loop continuously so agents improve safely after go-live.
Six-stage ADLC aligned to enterprise delivery
Experimentation loop between Code & Build and Test & Release
Runtime optimization loop between Deploy and Operate
Governance metrics, catalogs, and secure retirement
MCP + OpenTelemetry baked into the build phase
Agent Development Lifecycle (ADLC)
New tech-stack SDLC for AI agents - Build & Test (experimentation loop) and Deploy & Manage (runtime optimization loop).
1
Plan
Build & Test
Use case alignment, KPI definition, evaluation framework setup.
2
Code & Build
Build & Test
Agent development, enterprise system integration through MCP, observability with OpenTelemetry.
3
Test & Release
Build & Test
Run evals, calculate governance metrics, stage and certify in governed catalog.
4
Deploy
Deploy & Manage
Production rollout, multi-agent orchestration, infrastructure scaling.
5
Operate
Deploy & Manage
Performance optimization, continuous improvement against business KPIs.
Agents change after release: models drift, retrieval corpora grow, prompts evolve, and tools change. ADLC treats evaluation, observability, and governance as first-class - not optional ops afterthoughts.
Eval suites for accuracy, safety, latency, and cost
Staged promotion through a governed agent catalog
Runtime feedback into the next build cycle
Clear ownership for KPIs vs. model metrics
Experimentation & runtime loops
Between Test & Release and Code & Build, teams iterate on prompts, tools, and RAG quality. Between Operate and Deploy, production signals trigger scaled rollouts, canaries, and rollbacks - the runtime optimization loop.
Use Cases
Enterprise Gen AI CoE operating model
Regulated industry agent certification
Platform teams productizing internal agents
Managed agent operations (MLOps + LLMOps)
Technologies & Platforms
Azure AI FoundryPrompt / agent eval frameworksOpenTelemetryCI/CD + feature flagsMCP serversGoverned model catalogs
Frequently Asked Questions
Is ADLC the same as MLOps?
ADLC extends MLOps/LLMOps for agents: tool permissions, multi-agent orchestration, RAG quality, human oversight, and business KPI loops - not only model training pipelines.
Can Gensten run ADLC with our existing DevOps?
Yes. We plug eval gates and observability into your CI/CD, Azure DevOps, or GitHub Actions, and align release boards with your change-management process.
What is the experimentation loop in ADLC?
Between Test & Release and Code & Build, teams iterate on prompts, tools, RAG quality, and model choices until eval and governance metrics meet release criteria.
What is the runtime optimization loop?
Between Operate and Deploy, production signals (latency, cost, failures, KPI drift) trigger canary rollouts, rollbacks, prompt/index updates, and infrastructure scaling.
Which ADLC stage should we start with?
Always Plan: align the use case, define KPIs, and set the evaluation framework. Skipping Plan leads to agents that look impressive in demos but fail business outcomes.
How do evals work in Test & Release?
We run golden datasets for accuracy, groundedness, safety, latency, and cost; calculate governance metrics; then stage and certify the agent in a governed catalog before production.
How does ADLC handle regulatory audits?
Monitor includes ongoing audits, versioned prompts/models/tools, access logs, and secure retirement paths so auditors can see what ran, when, and under which policy.
Do we need a CoE to adopt ADLC?
A lightweight Gen AI / agent CoE helps, but ADLC can start with one product squad. We help define roles: product owner, agent engineer, data steward, and risk reviewer.
How often should agents be re-released?
Continuous small improvements are preferred. Material changes to tools, models, or corpora go through Test & Release gates; hotfixes can use accelerated paths with post-release review.
Where do MCP and OpenTelemetry fit in ADLC?
In Code & Build: MCP integrates enterprise systems as tools; OpenTelemetry instruments traces for prompts, retrieval, and tool calls so Operate/Monitor has real production signal.