Even a few very basic UML diagrams (Use Cases, Class, Sequence) can form a very effective introduction to a system.
I feel that people have just embraced Agile blindly and simply forgot about basic modelling.
I feel that people have just embraced Agile blindly and simply forgot about basic modelling.
Ultimately, you just create and endless amount of complex work that keeps developers continuously busy. On the bright side there's a never ending amount of tedious work wrestling systems back into some manageable form, on the downside that work is miserable, in my opinion because much of it can be removed whth proper planning. At some point, expectations eventually meet reality no matter how many developers management burns through, at some point it's clearly not an issue with technology, it's an issue with approach and project management. By that time the organization has had enough turnover in those above and below those pushing agile that those issues too can be hand waived away and the cycle repeats.
Very Good Point!
If you only look at things piecemeal and never holistically, the need for modeling and corresponding tools decreases.