>This just indicates a failure to perform a proper Analysis/Specification/Requirements phase, with relevant qualifications steps. It doesn't matter if you're a Manager or a lowly Developer - if you can't adequately qualify the requirements and specifications, the analysis is simply not complete.
Not really. It indicates a general inability to predict the future.
That's really the core of the issue. Requirements analysis can be done badly but even when done well it doesnt make you good at predicting the future.
The longer the feedback loop the more the ground changes under your feet.
>Pushing the problem to or away- from Managers is just one way of saying "I'm too lazy/incompetent to adequately complete the Analysis phase
I used to believe precisely this in my early 20s.
My "aha" moment came when I built software solely for myself and even then I realized that this didnt stop the requirements from changing because of surprises that kept being thrown my way and problems that I uncovered only in retrospect from actually using the software.
For sure not all problem spaces are this chaotic but most software problem spaces are.
Not really. It indicates a general inability to predict the future.
That's really the core of the issue. Requirements analysis can be done badly but even when done well it doesnt make you good at predicting the future.
The longer the feedback loop the more the ground changes under your feet.
>Pushing the problem to or away- from Managers is just one way of saying "I'm too lazy/incompetent to adequately complete the Analysis phase
I used to believe precisely this in my early 20s.
My "aha" moment came when I built software solely for myself and even then I realized that this didnt stop the requirements from changing because of surprises that kept being thrown my way and problems that I uncovered only in retrospect from actually using the software.
For sure not all problem spaces are this chaotic but most software problem spaces are.