|
• What are the key causes for business information system failure? • Why is the traditional approach most likely to cause failure? • How can you break the requirements-analysis-paralysis cycle? • How can you stop building stove-pipes and start building enterprise solutions? • How can you stop implementation contractors from delivering what’s not needed? • Why is the data-driven approach so much better than the process-driven approach? • Have can you stop packages from being such big, costly, unmodifiable let downs? • How do you know which business information systems to do and in which sequence? • Have can you make prototypes fast, efficient and effective? • How can you have a quality-engineered and proven approach? • How can you have an approach that’s data-driven and employs prototypes? • How can you have an approach that keeps “requirements organizations” in the driver's seat? • How can you have an approach that integrates business information system planning? • How can you have an approach that’s builds re-usable, integrated, non-redundant metadata? • How can you have an approach that integrates project management? • How can you have an approach that's reasonable to implement and has very high-value?
|
|