Agile system development, ca. 1973

Everyone has been talking about agile development for a few years now. That surprises me, because agility is nothing new, not even in system development. Among other things, this is documented in the INCOSE SE handbook, which the book Management of System Engineering by Wilton Perry Chase from 1974:
"Chase identified three simple criteria (...): Simplify communication, simplify controls, and simplify paperwork. Effective SE management is not achieved through formal, impressive, overwhelming documentation. It is achieved by creating a working environment that is capable of awakening and mobilizing all creative and inventive potential; that is geared towards living a holistic systems approach with a minimum of management baggage."
I believe that agility is experiencing a renaissance for two reasons: Firstly, because many companies have gone overboard with the formalization of processes (not least because of - well-intentioned - regulations). Secondly, there is now a great deal of standardization in agile procedures. This in turn means that there is a critical mass of trained personnel on the market who are also "interchangeable". In other words, employees do not have to be retrained when they are hired.
Even if it surprises me, I think these developments make sense in principle. Thanks to their widespread use, these ideas are now also being taken into account in the development of regulations. This is important, because an agile approach is necessary to be competitive in our short-lived times. But at the same time, we want to develop secure systems.
Incidentally, modeling is less popular at the moment - for whatever reason. I think that's a shame because the right kind of modeling can make agile working very efficient, as the model makes change management much easier.






