We must deal with the realities of requirements and configuration conflicts.
In today's environment, the majority of customers have a functional organizational structure where personnel are grouped by functional specialty, (example: sales, operations, human resources). This structure works well for division of effort and specialization. However, it does create challenges when managing business processes and the systems that support them. It is rare to see a business process that is completely supported by only one functional area. A functional requirement can add value to an individual group or function but can also have a negative impact across the business process/solution. A traditional packaged software implementation approach based upon functional silos will not identify these negative impacts until the testing phase at the end of an implementation. At this point, there are very few options available, and these negative impacts are usually...