proomt

Search

Search posts, papers, and topics

All posts

Made TechJames West4 min readintro

Taking advantage of the next acceleration curve

Summary

The post argues that agentic AI can compress the Discovery and Alpha phases of agile delivery from 12‑20 weeks to 8‑12 weeks by automating research synthesis, documentation, and prototyping. However, the real challenge becomes organizational governance and decision‑making, which must evolve to keep pace with the faster technical output.

  • Agentic AI can automate research synthesis, option analysis, documentation, and prototype generation, cutting discovery/alpha from 12‑20 weeks to ~8‑12 weeks.
  • Shorter phases free up time for user engagement and hypothesis testing, improving learning rather than reducing work.
  • The bottleneck shifts to governance and decision‑making; organisations must adapt leadership processes to match AI‑driven speed.
  • Human judgment remains critical for context, priorities, and stakeholder trust; AI augments but does not replace multidisciplinary teams.

Delivery leaders in public‑sector digital projects should care because AI can accelerate discovery phases but requires governance changes to realize speed gains.

5/10

Related reading

  1. No, You're Not Behind. But the Stage 3 Governance Window Is Closing.

    A four‑stage model for adopting agentic AI in software delivery pipelines, warning that Stage 3 (bounded autonomous execution) is arriving faster than governance programs. The post explains the stages, required controls (scoped credentials, fail‑closed defaults, tamper‑evident logs), and uses the OpenClaw incident as a cautionary example.

    Codeshipcloudbees.com9 min
  2. Changing the game: How Google uses agentic AI to secure hundreds of millions of lines of code

    Google’s AI & Infrastructure team built an agentic pipeline (Mantis) that runs pre‑submit AI‑driven scans on every code check‑in, validates findings with a fast triage agent (AST + call‑graph analysis) achieving >92% precision in <1 min, then auto‑generates fixes via a bug‑fix agent. Localized threat models and a two‑step scan cut false‑positives to ~3% and prevent hundreds of vulnerabilities eac…

    Google Cloud Bloggoogle.com4 min
  3. Agentic coding in the enterprise: Is your pipeline ready?

    Agentic coding lets AI agents write, test, and submit code autonomously, shifting the bottleneck from writing to governing code in production. Enterprises face rising failures, unclear ownership, growing costs, and weakened controls, which require a unified pipeline visibility layer.

    Codeshipcloudbees.com6 min
  4. Towards Self-Driving Codebases

    The post argues that AI agents could eventually handle low‑level engineering tasks—bug fixing, debugging, UI consistency, growth experiments—if the dev toolchain is made “agent‑legible”. It outlines missing primitives (global memory, code‑base rot prevention, better dev environments) and proposes a bootstrapping process to measure and improve a repo’s “agent readiness”. The piece is largely specu…

    Hacker News front pagedetail.dev9 minHN12099
  5. Agentic Skill Decay

    Addy Osmani warns that AI agents can short‑circuit the hands‑on practice (“reps”) that builds deep expertise and judgment. He recommends deliberately inserting hypothesis‑forming, “why” questioning, diff inspection, failure prediction, and occasional manual coding into the workflow, especially for junior engineers. A 2026 Anthropic study showed junior developers using AI scored 17 % lower on a fo…

    Addy Osmaniaddyosmani.com16 min
  6. Agentic DevOps World 2026: Key Takeaways

    Enterprise AI code generation is outpacing governance: 92% of leaders feel confident but 81% see more production issues; post‑generation stages (review, testing, deployment) are now the bottleneck. Successful adoption requires up‑skilling, end‑to‑end metrics, and tooling (e.g., CloudBees DevOps Agent Kit, PR‑auto‑approval agents).

    Codeshipcloudbees.com8 min