It is not a possibility that requirements and software configuration conflicts may arise, but rather it is a reality that these conflicts will arise. As the project team progresses in the business solution implementation, they will run against conflicts — both from a business and from a technology perspective. The best approach is to quickly identify these types of conflicts early, so that the project team has the time to correctly deal with these conflicts across the business solution.
To proactively identify requirements and software configuration conflicts, the project team needs to have the correct role for the job. Having a business solution architect in the lead will enable the implementation to focus across all levels of a business solution, in order to identify conflicts. These conflicts usually arise from functional focus that naturally occurs in business and during the implementation. If we look from a knowledge transfer perspective, we would agree that a single project...