AI in Software Delivery: articles & guides

A printed dashboard chart where the AI-adoption line climbs toward ninety percent while the cycle-time line runs flat across the quarters, annotated "flat".

AI Enablement

The PM AI Playbook: From Personal Productivity to AI Delivery Governance

The dashboard says ninety percent of the team is using the AI tools. More code is shipping than last quarter. Cycle time is flat, the review queue keeps growing, and a tester just flagged a defect that should have been caught two stages earlier.

A cork board pinning four connected developer harness artifacts: an AGENTS.md rules card, a feature requirements sheet, a test results sheet moving FAIL to PASS, and a progress handoff note

AI Enablement

The Developer AI Playbook: From Autocomplete to a Delegated Engineering Workforce

Most developers adopted AI and ran a delegated engineering workforce as a faster keyboard. Usage went up, review load went up, and cycle time barely moved. That is a role-design problem. The developer's new leverage is the harness the agent works inside, not the keystrokes per hour.

A four-layer code review workflow diagram: Layer 1 Before the PR, Layer 2 In-PR AI Advisory, Layer 3 Deterministic Gates, Layer 4 Human Judgment, with low, medium, and high risk arrows

AI Enablement

Code Review in the AI Era: From Human Bottleneck to Layered Quality Gate

Code review used to be one of the slowest steps in software delivery. AI did not fix that. It made it worse and more important at the same time. The redesign is not one AI reviewer replacing one human. It is a layered quality gate where every kind of risk has the right reviewer.

A user-story requirement card on a slate desk showing Given/When/Then acceptance criteria with one ambiguity flagged in the margin, a steel ruler laid across it for testability

AI Enablement

The AI Business Analyst's Real Job Moved Upstream, Into Business-Aligned, Testable Requirements

A business analysis function turns on AI story generation. Story count climbs, spec volume rises, time-to-draft falls. The one number that does not move is requirement-related rework. That is not a tooling problem. The BA role was never redesigned for a world where authoring is free.

A CTO's analytical cork board pinned with two anchor charts side-by-side: a flat velocity line over 16 sprints next to a clearly rising scope-per-point line, connected by a sticky-note…

AI Enablement

Story-Point Inflation and the AI Velocity Illusion

The CTO's velocity chart is flat. The team is shipping noticeably bigger scopes per ticket. Both numbers are true, and both come from the same backlog. Story points are a relative unit. AI changed what fits inside one. Reading flat velocity as flat productivity is reading the wrong instrument.

A QA practitioner seen over the shoulder marks up a printed priority sheet, deciding which product flows are worth testing, while a long generated test suite sits defocused on the monitor…

AI Enablement

AI Did Not Shrink the QA Role. It Moved It Upstream.

A QA function turns on AI test generation. Test counts, suite size, coverage all rise. Escaped defects stay flat. The team was promised faster quality and got faster activity instead. That is not an adoption problem. It is a design problem AI made visible.

Whiteboard flow diagram of seven "Quality Gates" in order: Tests, Lint, Types, Secrets, SAST, Coverage, Arch, with Arch circled as the "Human Gate".

AI Enablement

Quality Gates Under AI-Assisted Development

Code generation throughput rose. Review capacity did not. By the time the defect graph moves, the quality gate posture is months behind. Seven gates, in pipeline order, with named human owners, before the human reviewer is asked to catch everything AI generated.

Diptych: an onboarding UI form with Email, Password and Confirm Password fields and a Continue button, beside an Acceptance Criteria spec panel with four bullets

AI Enablement

Design-Driven Development: Prototypes as Constraints for AI Coding Agents

AI coding agents generate from briefs. When the brief is a text spec, every interaction surface gets filled with a plausible default - and the feature passes every check before a real user breaks it in three seconds.

Three-panel editorial dashboard under an OUTPUT DISTRIBUTION MANAGEMENT header: histogram with hallucination tail, weekly trend chart marked DRIFT, and output-channel map with a LEAKAGE…

AI Strategy

Hallucination, drift, and leakage are the same failure in different clothes

The demo works and the eval suite passes. Then production is always one more sprint away - because every AI fix breaks something else. That pattern has structure, and it is not about the model.

A hand-annotated decomposition diagram showing the four components of delivery cost as labeled zones: implementation cost, business complexity, coordination cost, review risk.

AI Enablement

AI Doesn't Just Make Developers Faster - It Changes What Complexity Means

Eighteen months into the agentic-coding wave, the question CTOs are asking has shifted from which tool to why the delivery numbers have not moved despite real adoption and real developer speed gains.

Four documents in a row labeling the four product decisions that set an AI feature's cost floor: Scope, Trust calibration, Retrieval, and Latency, joined by a line signaling interdependence.

AI Strategy

Cost discipline for AI products: token economics that do not bleed

Cost becomes a product problem before most teams notice the shift. By the time someone runs the unit economics on an AI feature, the design decisions that drove them are already shipped.

Eight printed engineering documents labeled with the SDLC stages Goal, Spec, Architecture, Implementation, Testing, Review, Gates, and Measurement, connected by a thin line.

AI in Software Delivery

Your SDLC Is One Stage Behind Your AI Tools

Ticket, code, review, test worked when senior engineers carried the goal, the architecture, and the risk in their heads. Coding agents cannot read minds. The work those four stages hid now has to become explicit, or the agent guesses.