It is a tale as old as, well, at least as software management.
We used to make software. Sometimes it went alright, sometimes not. Then someone wrote down a rough idea of different approaches to software projects and gave a simple example of a naive process on the first page. The managers went with that, because iterative stuff looked complicated.
Then, after years of pain, some people wrote the agile manifesto, because it was clear that we were not on the right path. Then some marketing/sales/manager types saw it and figured 'how can we make money of this, without understanding it? Oh, and how can we get those pesky developers out of the room, they are always correcting me when I lying, eh, selling to the customer!'.. And thus we got scrum, it's process and tools over EVERYTHING, but in the color of agile.
Not much different then the blackboard paradox I think. Can find it, but it goes like: A uni uses blackboard. Users rebel, adminstration caves and buys the new, user friendly blackboard alternative. Users settle down, the software get developed further, the company that makes it grows and starts to implement checkmark features for the admins that decide on purchasing. And thus the software becomes blackboard too.
It is a tale as old as, well, at least as software management.
We used to make software. Sometimes it went alright, sometimes not. Then someone wrote down a rough idea of different approaches to software projects and gave a simple example of a naive process on the first page. The managers went with that, because iterative stuff looked complicated.
Then, after years of pain, some people wrote the agile manifesto, because it was clear that we were not on the right path. Then some marketing/sales/manager types saw it and figured 'how can we make money of this, without understanding it? Oh, and how can we get those pesky developers out of the room, they are always correcting me when I lying, eh, selling to the customer!'.. And thus we got scrum, it's process and tools over EVERYTHING, but in the color of agile.
Not much different then the blackboard paradox I think. Can find it, but it goes like: A uni uses blackboard. Users rebel, adminstration caves and buys the new, user friendly blackboard alternative. Users settle down, the software get developed further, the company that makes it grows and starts to implement checkmark features for the admins that decide on purchasing. And thus the software becomes blackboard too.