That was the focus of a recent joint webinar hosted by 3Pillar and Forrester, titled AI & the SDLC: Beyond the Hype to a Practical Roadmap<\/a>.<\/strong> In a candid discussion, Lance Mohring<\/a> and Scott Young<\/a>, Field CTOs at 3Pillar, joined special guest Devin Dickerson<\/a>, Principal Analyst at Forrester, to explore what true AI-enabled velocity looks like – and how enterprises can prepare for it.<\/p>\n\n\n\n The conversation surfaced a clear message: success in the AI-driven SDLC isn\u2019t about chasing tools. It\u2019s about understanding maturity, orchestrating change, and building the right foundation for long-term impact.<\/p>\n\n\n To ground the discussion, 3Pillar introduced its AI-enabled SDLC maturity model – a framework designed to help technology and product leaders assess where they stand today and define the next step forward. <\/p>\n\n\n The model maps the evolution from today\u2019s fragmented experimentation to tomorrow\u2019s orchestrated, AI-native development environments:<\/p>\n\n\n\n \u201cWe built this to give leaders a way to visualize progress – to see not just what\u2019s possible, but what\u2019s practical today.\u201d<\/em> – Scott Young<\/p>\n<\/blockquote>\n\n\n While the framework spans five levels, most organizations remain early in the journey. Dickerson observed that maturity is uneven by nature.<\/p>\n\n\n\n \u201cYou might have a few developers running sophisticated agent workflows while others on the same team don\u2019t see the value yet. AI maturity isn\u2019t linear\u2014it\u2019s fragmented.\u201d<\/em> – Devin Dickerson<\/p>\n<\/blockquote>\n\n\n\n In other words, enterprise adoption today looks more like a patchwork than a transformation. Designers may experiment with AI for ideation; developers may use copilots for small code snippets. But without alignment, these efforts plateau quickly.<\/p>\n\n\n\n Young illustrated the point through a real example: after using an LLM to prototype a React app, he handed it off to a designer – who had no idea how to integrate it into Figma. \u201cWe\u2019re getting velocity at the individual level,\u201d he noted, \u201cbut we\u2019re not scaling collaboration.\u201d<\/p>\n\n\n\n This is the defining marker of Level 2: impressive local gains that don\u2019t yet translate into systemic value.<\/p>\n\n\n To explain this dynamic, Young used a powerful metaphor. In the early 1900s, when Henry Ford asked people what they wanted, they said \u201ca faster horse.\u201d<\/em> What they really needed was a car.<\/p>\n\n\n\n Many organizations are in a similar moment today – seeking incremental speed in legacy processes rather than reimagining the system itself. They\u2019re improving story writing, test automation, or code generation, but still within the same SDLC architecture.<\/p>\n\n\n\n \u201cThe real shift happens when you stop thinking about tools and start thinking about orchestration.\u201d<\/em> – Lance Mohring<\/p>\n<\/blockquote>\n\n\n When orchestration replaces isolated experimentation, the returns multiply. Moving from AI-assisted to agent-augmented workflows can unlock 10\u00d7 efficiency gains<\/strong> in focused use cases.<\/p>\n\n\n\n At this stage, humans shift from \u201cin the loop\u201d to \u201cover the loop.\u201d Instead of manually prompting each task, they oversee a network of agents performing coordinated roles – architect, tester, product manager, developer – each operating semi-autonomously.<\/p>\n\n\n\n This new structure changes more than output speed. It collapses the traditional seams of the SDLC, accelerates feedback loops, and forces organizations to rethink concepts like backlogs, sprints, and even technical debt.<\/p>\n\n\n\n \u201cTechnical debt may become less relevant. The AI doesn\u2019t care that your code isn\u2019t elegant\u2014it just makes the change everywhere instantly.\u201d<\/em> – Scott Young<\/p>\n<\/blockquote>\n\n\n\n But acceleration without governance can magnify risk. Trust, quality, and validation processes must evolve just as quickly. \u201cDid we build the right thing?\u201d remains the most important question.<\/p>\n\n\n In the next phase of maturity, the SDLC becomes less about humans instructing narrow task agents and more about planning agents coordinating entire workflows.<\/p>\n\n\n\n A task agent might add a new field to a form; an planning agent could translate a product requirement document into a full sprint backlog, direct subordinate agents to execute each story, and verify completion – all under human supervision.<\/p>\n\n\n\n \u201cWe\u2019re moving from delegating tasks to delegating responsibility\u2014while humans retain accountability.\u201d<\/em> – Devin Dickerson<\/p>\n<\/blockquote>\n\n\n\n This evolution redefines roles. Product managers, architects, and designers become system conductors rather than task executors. The orchestration layer becomes the new frontier of competitive advantage.<\/p>\n\n\n The speakers closed with four practical recommendations for leaders beginning this journey:<\/p>\n\n\n\n \u201cAI in the SDLC isn\u2019t a single project – it\u2019s an organizational transformation that demands structure, experimentation, and empathy in equal measure.\u201d<\/em><\/p>\n<\/blockquote>\n\n\nThe AI-enabled SDLC maturity model<\/strong><\/h2>\n<\/div>\n\n\n
![\"\"](\"https:\/\/www.3pillarglobal.com\/wp-content\/uploads\/2025\/11\/3Pillars-AI-Enabled-SDLC-Maturity-Model_cropped-1024x527.png\")
<\/figure><\/div>\n\n\n\n
<\/li>\n\n\n\n
<\/li>\n\n\n\n
<\/li>\n\n\n\n
<\/li>\n\n\n\n\n
Where most organizations are today<\/strong><\/h2>\n<\/div>\n\n\n
\n
The \u201cfaster horse\u201d moment<\/strong><\/h2>\n<\/div>\n\n\n
\n
What true AI velocity looks like<\/strong><\/h2>\n<\/div>\n\n\n
\n
From task agents to planning agents<\/strong><\/h2>\n<\/div>\n\n\n
\n
Turning insight into action<\/strong><\/h2>\n<\/div>\n\n\n
\n
<\/li>\n\n\n\n
<\/li>\n\n\n\n
<\/li>\n\n\n\n\n