Because both articles are talking about the same. Thieves.
For me agile is embezzlement.
Waterfall has a reason to be: taking enough precautions to make sure costing and feasibility of a feature would fit the (internal or external) customers' needs and budget (as specified per contract). Without obligation of results you have an obligation of means (it is what professionalism is supposed to be : to be liable).
After Agile, project are ALWAYS delivered on time. Not 100%, but they are "built to budget".
Sometimes the 10% missing are like not possible and the heart of the feature. But who cares? Product are not tested anymore, and defects are just now in the support budget.
The application has a nice reactive angular interface and a mobile declination. And the customers like in a marketing trick are "empowered". The IT department always look busy with a constant pipeline of activity that is so successful it requires even more headcount.
The fact the software was delivered with constant modification on which the customers was spammed with more or less relevant remarks that made him loose focus on his initial goal is irrelevant. Staging, delivering is now part of the past with meaningful version numbers. It is just constant delivery.
It is for the customers' own goods.
The company also loses track of its costing pricing and investment.
Too much information kills the information.
That what agile is : a smoke screen for embezzling a budget in a politically and acceptable way.
I wonder if there are still any accountant in modern IT companies or if everyone decided to stop counting how much companies lose and win every months.
It is as if IT is totally living on another economical planet where investments are not required to be justified, and products don't need to be fool proofed against contractual penalties applied to non conformities. If so, it means we don't have any customers paying.
And of course, in the turmoil of micromanagement, new "new techs from the 70s" are micro introduced during the scrum making part of the management pushers of the products they have been nicely solicited to use by nice vendors inviting them to superb conferences and formation that are not called bribing but social networking.
This result in making developers gain as much values in "specialized tools" as they are losing global knowledge of the chain of value and disorganizing most of the profession.
You never noticed Scrum and scam sounded the same?
For me agile is embezzlement.
Waterfall has a reason to be: taking enough precautions to make sure costing and feasibility of a feature would fit the (internal or external) customers' needs and budget (as specified per contract). Without obligation of results you have an obligation of means (it is what professionalism is supposed to be : to be liable).
After Agile, project are ALWAYS delivered on time. Not 100%, but they are "built to budget".
Sometimes the 10% missing are like not possible and the heart of the feature. But who cares? Product are not tested anymore, and defects are just now in the support budget.
The application has a nice reactive angular interface and a mobile declination. And the customers like in a marketing trick are "empowered". The IT department always look busy with a constant pipeline of activity that is so successful it requires even more headcount.
The fact the software was delivered with constant modification on which the customers was spammed with more or less relevant remarks that made him loose focus on his initial goal is irrelevant. Staging, delivering is now part of the past with meaningful version numbers. It is just constant delivery.
It is for the customers' own goods.
The company also loses track of its costing pricing and investment.
Too much information kills the information.
That what agile is : a smoke screen for embezzling a budget in a politically and acceptable way.
I wonder if there are still any accountant in modern IT companies or if everyone decided to stop counting how much companies lose and win every months.
It is as if IT is totally living on another economical planet where investments are not required to be justified, and products don't need to be fool proofed against contractual penalties applied to non conformities. If so, it means we don't have any customers paying.
And of course, in the turmoil of micromanagement, new "new techs from the 70s" are micro introduced during the scrum making part of the management pushers of the products they have been nicely solicited to use by nice vendors inviting them to superb conferences and formation that are not called bribing but social networking.
This result in making developers gain as much values in "specialized tools" as they are losing global knowledge of the chain of value and disorganizing most of the profession.
You never noticed Scrum and scam sounded the same?