Agile development might be 25 years old, but it’s withstood the test of time – and there’s still more to come in the age of AI
The methodology transformed software development, and it's still alive and kicking
Sign up today and you will receive a free copy of our Future Focus 2025 report - the leading guidance on AI, cybersecurity and other IT challenges as per 700+ senior executives
You are now subscribed
Your newsletter sign-up was successful
“I couldn’t imagine it being more impactful,” Jon Kern, co-author of the Agile Manifesto tells ITPro. 25 years on and Kern firmly believes the manifesto – and methodology at large – has withstood the test of time.
Alongside 16 other co-authors, Kern helped curate the Agile Manifesto in February 2001 during a series of crunch meetings at Snowbird ski resort in Utah. The goal was simple: streamline development by combatting “heavyweight processes” which burdened devs and slowed down software delivery cycles.
“It promoted lighter, easier ways of developing software by capturing what a small group of practitioners had in common, and making those attitudes available to others who were struggling under heavyweight approaches,” he told ITPro.
The inspiration behind the manifesto lay in long-running gripes with traditional development approaches such as Waterfall. According to Jon Rimmer, CXO at Mercator Digital, this approach was rigid, inefficient, and at times painfully slow.
A key factor here is that under this methodology, teams worked through phases in a linear fashion, with each of these required to be completed before moving on.
“The traditional ‘Waterfall’ approach meant you could spend six months planning - and then a further three years building - only to be completely divorced from the end users and the real environment,” Rimmer told ITPro.
With Agile development, however, flexibility and adaptability were key focus areas. The 12 central principles outlined in the manifesto prioritized an array of factors, including faster delivery times through now-iconic ‘sprints’, rolling testing processes, continuous feedback, and smaller, more efficient teams.
Sign up today and you will receive a free copy of our Future Focus 2025 report - the leading guidance on AI, cybersecurity and other IT challenges as per 700+ senior executives
Martin Reynolds, field CTO at Harness, told ITPro that the impact of Agile was “huge” when it hit the scene, adding that it highlighted and emphasized what efficient teams were already doing at the time.
“I’m old enough to remember when the Agile Manifesto launched – I was coding at the time – and its impact was huge,” he said.
“What it really did wasn’t to invent anything radically new, but codify what the best teams were already doing,” Reynolds added. “It gave the industry a common framework to move away from Waterfall, long release cycles, heavy documentation upfront, and very little ability to change course once things were underway.
“I can vividly remember projects where half the time was spent writing specs, only to hope everything fitted together months later. Agile flipped that on its head.”
What did Agile development actually improve?
Key focus areas of the Agile Manifesto helped drastically simplify software development, Reynolds noted.
By moving teams to smaller more regular releases, for example, this “shortened feedback loops” typically associated with Waterfall and improved flexibility throughout the development lifecycle.
“That reduced risk made it easier to respond to customer and business needs, and genuinely improved software quality,” he told ITPro. “Smaller changes meant testing could happen continuously, rather than being bolted on at the end.”
The longevity of Agile methodology is testament to its impact, and research shows it’s still highly popular. A survey from Forrester in early 2025 found 95% of respondents highlighted Agile practices as critical to their organization.
Notably, 58% of respondents said they’re still prioritizing adoption of Agile practices, underlining its continued popularity among business and technology professionals.
Manageable drawbacks
That’s not to say Agile doesn’t have some drawbacks, however. Reynolds noted that areas such as technical debt can become a burden due to the rapid nature of this approach.
“When teams are under constant pressure to deliver new features, debt can easily be pushed to the bottom of the backlog,” he told ITPro. “The problem is it doesn’t age well – it’s not like wine. It’s more like milk: the longer you leave it, the worse it smells.”
Moreover, scaling Agile across larger organizations has proved troublesome over the course of its lifespan. As ITPro previously reported, Digital.ai’s 2024 State of Agile survey found larger enterprises encountered significant challenges embracing Agile.
Simply put, the larger the company, the more fragmented teams become. This results in a scattered approach where some teams fully embrace the methodology while practices fall by the wayside in others.
Agile in the age of AI
With the rapid enterprise adoption of generative AI over the last three years, Agile methodology has once again been thrust into the spotlight.
Findings from Digital.ai’s 2025 State of Agile Report found AI is now helping supercharge Agile development, with teams using an array of tools to underpin and support processes.
More than three-quarters of respondents said they’re using AI to “save time or reduce manual effort”, for example, using the technology to auto-generate documentation or summarize retrospectives.
According to Kern, AI and Agile are “a match made in heaven” and the advent of the technology means this approach is no longer optional, albeit with a notable caveat.
“You need it more than ever,” he said. “You can build so much more in less time, which can also magnify potential pitfalls if you’re not careful. The speed of delivery with AI can easily outpace feedback, but that’s an exciting opportunity, not a flaw.”
Reynolds echoed those comments, noting that while Agile can be a force multiplier for teams, there are still risks – particularly with the influx of AI-generated code in software development.
“Those gains are often offset downstream, creating more bugs, higher cloud costs, and greater security exposure. The real value comes when AI is extended beyond code creation into testing, quality assurance, and deployment,” he said.
“Applied thoughtfully, it strengthens the fast feedback loops that Agile depends on and helps teams adapt more confidently as business requirements change,” Reynolds added.
“In that sense, AI doesn’t replace or outdate Agile – it reinforces the principles that have kept it relevant for the past quarter of a century and will ensure it remains so long into the future.”
FOLLOW US ON SOCIAL MEDIA
Make sure to follow ITPro on Google News to keep tabs on all our latest news, analysis, and reviews.
You can also follow ITPro on LinkedIn, X, Facebook, and BlueSky.

Ross Kelly is ITPro's News & Analysis Editor, responsible for leading the brand's news output and in-depth reporting on the latest stories from across the business technology landscape. Ross was previously a Staff Writer, during which time he developed a keen interest in cyber security, business leadership, and emerging technologies.
He graduated from Edinburgh Napier University in 2016 with a BA (Hons) in Journalism, and joined ITPro in 2022 after four years working in technology conference research.
For news pitches, you can contact Ross at ross.kelly@futurenet.com, or on Twitter and LinkedIn.
-
Will a generative engine optimization manager be your next big hire?In-depth Generative AI is transforming online search and companies are recruiting to improve how they appear in chatbot answers
-
European Commission clears Google’s Wiz acquisition, citing 'credible competition' from Amazon and MicrosoftNews Regulators said there are “several credible competitors” to Google regardless of the acquisition
-
AI is transforming Agile development practices as teams battle mounting delivery cycle pressure and ROI concernsNews The influx of AI tools is helping reshape Agile development at a critical juncture for the methodology
-
Java developers are facing serious productivity issues: Staff turnover, lengthy redeploy times, and a lack of resources are hampering efficiency – but firms are banking on AI tools to plug the gapsNews Java developers are encountering significant productivity barriers, according to new research, prompting businesses to take drastic measures to boost efficiency.
-
Why the CrowdStrike outage was a wakeup call for developer teamsNews The CrowdStrike outage in 2024 has prompted wholesale changes to software testing and development lifecycle practices, according to new research.
-
Why are so many AI projects destined for failure? Inexperienced staff, poor planning, and a shoehorned approach to agile development are all stifling innovationWhile agile development practices work well in many circumstances, devs are encountering serious problems applying the methodology in AI projects
-
‘It’s time to question agile’s cult following’: Doubts cast on method’s future, with 65% of projects more likely to failNews Agile development methods just aren’t delivering, and it's time devs acknowledged its failings
-
Agile development has a security problem - and developer ‘champions’ could be the key to ensuring safer softwareAnalysis Security considerations can be an afterthought in agile development, but there are ways to address the issue and prevent disastrous consequences
-
Agile development is fading in popularity at large enterprises - and developer burnout is a key factorNews Firms employing agile development practices are ‘having difficulty adapting’ in a new world of developer burnout, AI and more, a new report claims
-
What is platform engineering and will it see the end of DevSecOps?In-depth Platform engineering is not just the latest industry buzzword but could represent a profound change in how software is developed and governed