The AI-Fluent PDLC
Read this paper if
- Nearly everyone on your team has an AI subscription
- Cycle times have not reduced and overall productivity gains are elusive
- You'd like a framework on how to move your team to AI fluency
Short on time?
Who this is for
A field reading built on public research and our work with regulated teams, not a controlled benchmark. Lifecycle figures are Incubyte’s analysis of enterprise health-tech clients’ pipeline.
The Offer.
01
SECTION ONE · 01 / 07
Adoption is not fluency
AI spends are concentrated on a small sliver of the delivery cycle associated with writing code. Productivity gains are realized when the entire cycle is compressed.
- Usage up, delivery unchanged
- Coding is not the constraint
- Fluency is speed + trust
- Usage up, delivery unchanged
- Coding is not the constraint
- Fluency is speed + trust
DORA’s 2025 survey of nearly 5,000 technology professionals found that 90% now use AI at work. Most tellingly, higher AI adoption was found to be associated with both, higher software delivery throughput and also higher delivery instability. This led DORA to conclude that AI is fundamentally an amplifier: it magnifies the strengths of high-performing organizations and the dysfunctions of struggling ones.
AI has been unable to compress the entire cycle, with faster coding creating bottlenecks upstream and downstream.
The next chapter introduces the core organizational framework required to propel this journey from adoption to fluency.
One caveat before we go further. Since AI amplifies the current state, the system has to be in a state that’s worth amplifying. Continuous delivery, automated tests, small batches, and loosely coupled architecture are table stakes that let teams compound their AI gains. When missing, teams are adding code at a speed that the system can’t absorb. Everything that follows assumes these foundations are in place.
90%
7.8%
14%
02
SECTION ONE · 02 / 07
The fluency stack
CAPABILITY
CONDUCT
The AI-Fluent stack, bottom to top
FIG. 02 · THE AI-FLUENT STACK
03
SECTION THREE · 03 / 07
The capability layer
- Learning and continuous improvement
- Skill and judgement
- Business fluency
- Knowledge and documentation systems
Culture decides whether any capability takes root
If it isn’t safe to push back when management demands higher AI usage, your stability numbers will soon be doing that job for you.
Learning and continuous improvement
Leaders have to supply the conditions that enable learning:
01
Slack Time
02
Learning Budget
03
AI-Centric Hiring
04
Cross-functional Pairing
Active pairing across product, development and QA, so teams think of business outcomes and not just ticket completion.
Apprenticeship matters more in the AI era. AI is doing the work juniors used to learn from, so you have to maintain a healthy senior-to-junior ratio and build new learning loops on purpose, or you’ll have no senior engineers in five years.
Skill and judgement
The center of gravity of engineering skill is shifting from producing code to having AI produce it well, evaluating it, and doing this with the least amount of rework.
01
Reading and judging AI output
Evaluating large AI-generated plans, diffs, and code for correctness and fit. This is fast becoming the core engineering skill, and what the hiring process should test for.
02
Spec and intent authoring
Telling AI what to build clearly enough to get the right result: specifications, constraints, and acceptance criteria. Drive the transition to spec-driven development to leap past prompt-in, code-out.
03
Architecture and systems judgment
Recognizing good structure when you see it and steering AI toward maintainable design instead of plausible mess.
04
Generalist breadth
A wide surface area across the stack and the SDLC, so one person can direct AI across more of the work and connect the parts.
05
Craft mindset
Caring enough to ensure that the bar is set high for AI generated code, and quality of the codebase doesn’t degrade over time.
One of DORA’s seven AI capabilities is a Clear and communicated AI stance. The stance is enforced when the team has the skills and judgement to do so.
Business fluency
As AI absorbs the purely technical work, the edge that’s left is the knowledge AI can’t pull from the codebase or a prompt: how the business actually makes money, how this organization actually works, and the rules of the domain it operates in. With role boundaries blurring across product, engineering, and QA, each person own outcomes and that makes it critical for everyone to be fluent in what problems they are solving for their end users. This fluency is what lets a person direct AI toward the right decisions, and it is what keeps a system built around its domain rather than assembled in isolation.
Decisions grounded in how the business and the system actually work, not just the code, predict rework rate and value delivered. Teams with that grounding build the right thing the first time, making a huge impact on their overall cycle time.
Another of DORA’s seven capabilities, user-centric focus is what business fluency enables, and ensures that AI-accelerated teams are moving quickly in the right direction.
66%
75%
would still ask a person when they don’t trust an AI answer · Stack Overflow 2025
~95%
AI commoditizes the tech; the edge is what lives outside the codebase, in your business, your domain, and your engineers’ heads.
Knowledge and documentation systems
The first three dimensions are more about capabilities your people build. This one is about the systems that capture what the organization knows and makes relevant context available to both humans and agents. A model with no access to your architecture decisions, your domain glossary, your past incidents, or your coding standards will produce something generic. The same model, grounded in that context, produces something that fits with minimal reviews and rework.
With the reasoning behind choices written down, the “why” survives past the person who made the call, and is available to agents as invaluable context.
The practices, patterns, and domain rules your best engineers live by, become reusable skills, commands, hooks, and shared memory that every agentic session inherits.
Codifying craft is how a team's best practices stop being tribal knowledge and become the default.
Modernization is now an AI prerequisite.
Code is the best form of documentation and coding agents can only go as deep as your codebase lets them. A legacy, undocumented, tightly coupled codebase keeps a team stuck at lower levels of fluency, no matter how good the capabilities are. Getting a codebase agent-ready, through documentation, decoupling, and test coverage, is a precondition for fluency, and a subject big enough for its own companion paper.
What’s good for your engineers is good for your agents. Clear documentation and clean code help both; the messy kind drags both down. AI will quickly help you find out where you stand.
04
SECTION FOUR · 04 / 07
The Conduct Layer
The enforcement half of fluency: standards, regulations, and data boundaries held while AI generates code, ensuring manual reviews are not the bottlenecks.
- Coding standards
- Compliance posture
- Data and security boundaries
- Coding standards
- Compliance posture
- Data and security boundaries
The capability layer prepared your people and systems for AI. The conduct layer ensures your standards, regulations, guardrails, security rules, data boundaries, are all enforced while AI generates code. The cost of a leak missing human reviews could be catastrophic for a highly regulated domain, and conduct is what reduces the risk.
Coding Standards
01
Session-loaded rules
02
Org-wide and repo-specific layers
03
Craft with AI
If your standard only lives in review comments, you are paying your best engineers to be a linter.
Compliance posture
01
Regulations encoded as guardrails
The frameworks that apply to you, written into rule sets the agent works to as it generates.
02
Audit trails and logging
Logging every prompt, action, and policy decision as the work happens ensures the evidence is always available.
03
DORA's strong version control practices
When every change is small, attributable, and logged with its reasoning, your version history becomes the additional compliance record.
Compliance checked only at review is you relying on the judgement of one human. It takes just one incident to put your business at a serious risk.
Data and security boundaries
01
In-flight detection
02
Tool and action governance
03
Own the data boundary
One prompt with real patient data in a public model is enough to lose your AI mandate. Boundaries are what let you go faster with higher trust in autonomy.
Compliance and audit posture
Conduct has to live at the point of generation, not at the time of PR reviews or quarterly audits.
05
SECTION FIVE · 05 / 07
Engineering performance
Higher engineering performance is evidence that your capability and conduct layers have been built right.
- Throughput and cycle time
- Stability
- Code quality and technical debt
- Compliance and audit-readiness
The four DORA metrics: deployment frequency, lead time, change failure rate, and time to restore, track the system’s health and measure a team’s ability to ship fast with safety. An AI-assisted PDLC raises the stakes as there’s a lot more code being generated, and this makes it even more critical to get early signals from these metrics as adoption grows. These are also the right signals on how the team is trending on its journey from adoption to fluency.
When the Capability and Conduct dimensions are done right, all four DORA metrics move together.
Figure 3. DORA metrics mapped to their key capability and conduct drivers
01
Throughput and cycle time
The whole cycle compresses, not just the coding sliver.
02
Stability
Change failure rate and time to restore hold as throughput climbs.
03
Code quality and technical debt
The codebase stays ownable months later with sustained developer and agent experience
04
Compliance and audit-readiness
Compliance posture stays intact with evidence always available.
The next chapter defines our model for fluency and how these performance parameters translate to your team’s AI fluency.
06
SECTION FIVE · 05 / 07
Reading your fluency
Fluency has two axes: how fast you move across the cycle, and how much of your trust AI has earned.
- Fluency is fast plus trusted
- Flow, level by level
- Earned trust
A team can feel fluent and yet, not be.
They may be shipping fast, with healthy dashboards, and high tool usage. Then a change that sailed through review takes down production, and it turns out nobody really knew what the AI had written. That gap, between feeling fluent and being fluent, is what this section helps you see.
Fluency is fast plus trusted.
Fluency is fast plus trusted.
Earned trust is only one axis. A team can be correct and sure of it and still be slow, hand-reviewing every change. Cross earned trust with flow, how much of the cycle you’ve actually compressed, and fluency falls out as one corner: the top-right, fast on trust you’ve earned.
FLUENT
Safe but stuck
Reckless
Stalled
Flow: the whole cycle moving without friction
Work is in flow when a unit of work moves through the whole delivery cycle without stalling: no waiting in a queue, no bouncing back for clarification, no sitting in a review backlog for three days. When work flows, cycle time is low. When it keeps stopping, cycle time balloons, and you get our healthtech client from Chapter 1: 11 of their 11.7 weeks spent stalled, with actual coding taking just 6% of the cycle.
Earned Trust: Confidence that matches reality
Confidence on its own tells you nothing, because a team can feel completely sure and be completely wrong. What matters is whether that confidence is calibrated: whether what the team believes about its AI’s output matches what the code actually does.
You reach the top-right by building capability and enforcing conduct as AI works across the cycle. They’re the only levers that move flow and trust together, faster delivery you don’t have to second-guess.
The 3-point summary
Software teams have adopted AI fast, but benefits are still anecdotal. This paper examines why, and what separates the teams that convert AI into delivery gains, from those that do not.
AI Adoption
A large part of the AI budget is currently spent on coding, which is a fraction of the entire delivery cycle. This is why productivity gains are elusive and cycle times are largely unchanged. There are spikes of productivity across the org but these are not predictable and sustained.
Foundations for Fluency
Fluency rests on two organizational layers. Capability - the culture, learning, judgement, and documentation practices that let people direct and check AI across the lifecycle. Conduct, the standards, regulatory rules, and guardrails enforced while AI generates code.
Achieving Fluency
Fluency is when the full delivery cycle is compressed without losing trust in what ships. It can be measured by how much a team trusts the AI-assisted work, along with how much they've been able to reduce their cycle time and enable flow. It can be achieved when organizations build their capability and conduct around AI.
Answer six questions to understand where your team stands on their journey from adoption to fluency
THE OFFER • TWO WAYS TO INSTALL IT
Buy it from Anthara
Augment your team's capabilities and introduce the conduct layer, as a product. Fully deployed within your security boundary.
Build it with Incubyte
Our forward deployed engineers build your capability and conduct layers for you, alongside your team.
Methodology and sources
References
1
Delivery lifecycle timings (coding ≈6% of the cycle, 4.68 days inside an ~11.7-week cycle) are from Incubyte's analysis of an enterprise health-tech client's delivery pipeline.
11
Peng et al., The Impact of AI on Developer Productivity: Evidence from GitHub Copilot, 2023; Cui, Demirer, Jaffe, Musolff, Peng, and Salz, field experiments on generative AI and developer output.
The Agent Experience Audit