When product and engineering leaders at frontier AI companies give guidance to developers on how to succeed with AI, the lessons they share are the same ones Agile software development first promoted 25 years ago: Deliver working software frequently, let customer feedback and real-world usage guide development, and prioritize lightweight, continuous alignment and coordination.
Let Usage Guide Product Direction
One product lead at a frontier AI lab described how shifting from multi-quarter roadmaps to daily shipping meant learning to prioritize rapid, real-world feedback over upfront plans. Their team ships features as “research previews,” which is what they call experiments designed to gather feedback rather than finished products. Similarly, an engineering lead on a popular AI coding assistant shared how their product took months of real-world exposure before people understood what it was good for. Their takeaway was to start small by building the smallest possible product so actual customer usage could teach them what to build next.
These recommendations echo the goals of Agile, which is not just about going faster, but also a strategy to avoid building the wrong thing.
Traditional planning treats detailed specifications as a means of eliminating uncertainty, whereas Agile aims to reduce uncertainty by using early releases to capture feedback and accelerate learning.
From the Manifesto for Agile Software Development:
- Value: Working software over comprehensive documentation
- Principle: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
- Principle: Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
- Principle: Simplicity—the art of maximizing the amount of work not done—is essential.
- Principle: Working software is the primary measure of progress.
Speed Without Alignment Generates Waste Faster
Because generating code has become incredibly cheap and fast, the speed of software development has accelerated to the point where every other activity risks becoming a bottleneck.
To maintain high development velocity, developers may be inclined to maximize time spent building. But when teams stop writing PRDs and requirements or attending design reviews and planning meetings, alignment gaps become visible only after code is completed and deployed. The alignment gap causes teams to ship disconnected features, duplicating effort, and realizing they’ve built the wrong thing only after the code is deployed. Faster development makes poor alignment more expensive.
Unconstrained velocity accelerates waste. Agile can help by replacing heavy, upstream review gates with lightweight, continuous alignment. Practices like user stories and user story mapping aren’t just artifacts, they’re lightweight and effective techniques for team conversations and coordination.
From the Manifesto for Agile Software Development:
- Principle: The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
Remove Process, Hire for Taste & Mindset
Teams, whether AI-augmented or not, go fast by relying on shared alignment on principles rather than heavy processes or approvals. They hire members with strong product taste. When developers understand their users’ needs, teams can eliminate overhead processes and ship more quickly.
From the Manifesto for Agile Software Development:
- Value: Individuals and interactions over processes and tools
- Principle: Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
- Principle: The best architectures, requirements, and designs emerge from self-organizing teams.
- Principle: Business people and developers must work together daily throughout the project.
- Principle: Continuous attention to technical excellence and good design enhances agility.
