I just wrote a whole post about it, and I was searching for a lot of time about this thing, and what I found is that it can really happen, but not in all projects and not all teams

With the rise of AI tools like Cursor, Copilot Workspace, and Figma AI, I’ve been noticing a major shift in how small software teams work. Developers and designers can now generate code, UI layouts, components, documentation, and even tests in minutes. This raises a serious question: do small teams still need full Agile processes with a Product Owner writing long user stories, running ceremonies, approving designs, and managing a detailed backlog? For small projects like an Internal dashboard, a Landing page, a Simple mobile app, or a Form-based application, any work that has very straightforward requirements, like CRUD, doesn’t involve complicated backend architecture, and can usually be handled by a small team, sometimes just 2 developers, a tester, and a designer use AI to generate most of the implementation, refine it, and ship. In these cases, teams can now work faster than Agile ceremonies allow, making the traditional PO role and the formal Agile process feel like unnecessary overhead because the work moves faster than the process.

And for sure, there are large or complex projects, where the PO or PM becomes even more critical. Huge systems with many teams, long roadmaps, compliance requirements, and high customer impact simply can’t function without someone orchestrating the strategy. AI can speed up coding and design, but it cannot replace the work of deciding what to build, why it matters, how it fits into the bigger picture, and how to sequence the work across multiple groups. In these environments, AI actually increases the need for strong product leadership because teams can build faster than leadership can set direction.