The dust had not even settled, but the screaming tantrum was already well underway. Yet another project had crashed and burned, and yet another group of users had been let down. Nothing happens without a reason, but uncovering why a project fails can be both complex, confusing and frustrating. Without a thorough (and sometimes painful) post-mortem, nothing will really be learned. This session tells the story of one such failed BI project.
We will explain what went wrong, pick apart why it went wrong, use those insights to create a new architecture, and finally walk through the steps taken to make the follow-up project a great success. This session is all about learning from the mistakes made, and how insight can often be found where you might not expect it. You will leave with an insight into why many technical projects fail, how relatively small changes can mean the difference between disaster and success, and why some technical problems aren't technical problems at all.