A counter to this is "requirements change quickly, therefore the system needs to change quickly too." But the actual case is: most organizations don't really know how to do systems analysis. So this results in one of two scenarios: either the organization wastes a lot of time and money in the analysis phase struggling to do what they cannot, or they punt on requirements analysis altogether and wait for requirements to surface at implementation time. This is called "Agile" today, but was described by Milt in 1983: "do a superficial feasibility study, do some quick and dirty systems design, spend a lot of time in programming, install prematurely so you can irritate the users sooner, and then keep working on it till you get something accomplished."
PRIDE is like a textbook on how to build a system, from requirements analysis through design, implementation, and maintenance. It was the first methodology for doing so, and it transformed information systems from arcane art into a proven, repeatable science. It should be the industry standard, but is now at risk of being forgotten, largely due to programmers holding the industry hostage.
AI is taking programmers out of the equation. PRIDE is relevant again.
Maybe that will change with LLMs, but you’ve got the causality arrow backwards. Systems analysts didn’t disappear because of Agile; Agile exists because that way of working didn’t work.
Source: I was on the front lines of the first Agile wave starting in late 1999.
(And then what people actually adopted as “Agile” generally wasn’t what was created by the first wave of the Agile community, but that’s a whole ‘nother topic.)
Milt realized as early as the 1970s, if not long before, that programmers had way too much power in an organization because most organizations adopted a "tool-oriented approach" to computer technology: here's a tool, how do we make use of it? They let the programmers run wild, and the result was software that was a buggy mess. What's needed is a management-oriented approach in which the management of the company calls the shots on what's needed for the company to function.
In PRIDE, the systems analyst is centered. This is explicitly a business role, not a technical role, and their job is to understand the business in such a way that the information systems (not programs, nor apps) that drive the business can be described in diagrams and text. Only once the requirements, definitions of terms, and data definitions have been established and standardized can the implementation phase begin. Bryce estimated that if you're not spending 65% of the effort in systems analysis and only 15% of the effort in programming, you're doing it wrong.
This is how grown-ups did information systems for decades. And then the internet happened, "hacker culture" happened, and the programmers were back in the driver's seat, producing things like "Agile".
Now we have AI, and to quote another commenter elsewhere in the thread, the programmers have had their tails cut off. That 15% number asymptotically approaches zero. But the systems analysis still needs to be done, and for the foreseeable future anyway, that needs a human touch.
Become a business person, not a "software engineer". They are the ones who will drive things forward in the agentic era.