"The business and developers need to work together to create a set of requirements that doesn't map the processes as they are, but maps the processes as they should be."
And therein lies the problem.
In the current ERP industry, you have 100 vendors, 10,000 programmers, 20,000 salesmen, and 6 people who know how to define requirements "as they should be". So you do what any sleight of hand expert does: you change the agenda.
"Do you really want to risk your audit if you don't buy software from my brother-in-law?"
And therein lies the problem.
In the current ERP industry, you have 100 vendors, 10,000 programmers, 20,000 salesmen, and 6 people who know how to define requirements "as they should be". So you do what any sleight of hand expert does: you change the agenda.
"Do you really want to risk your audit if you don't buy software from my brother-in-law?"