How Agile is Your Business Intelligence?
[This is something of a 'live-blog'. Yesterday I had the chance to watch a webcast on 'Nimble Business Intelligence' and I jotted down some of my favorite highlights from the presentation.]
You know 'BI', right? In a recent report Gartner described Business Intelligence (aka BI) as software that delivers 13 capabilities: Reporting, Dashboards, Ad hoc query, Microsoft Office integration, Search-based BI, BI infrastructure, Metadata management, Development, Workflow and collaboration, OLAP, Advanced visualization, Predictive modeling and data mining, Scorecards. This dirty dozen featureset certainly covers a lot of functionality and all of it is for 'decision-support'.
But considering the high failure rate of traditional BI projects, maybe BI alone isn't enough. In a webcast titled 'Nimble BI: Enterprise Mashups for Agile Intelligence', BI expert Seth Grimes addressed what he thinks is an under-served area of decision-support: agile or 'nimble' intelligence that supports the more dynamic decision-makers. And like the title of the event says, enterprise mashups are the way to get your agile intelligence.
Early in his presentation Seth showed a bunch of 'composed' dashboards from popular BI vendors, created by one group for consumption by another group. He emphasized the word 'composed'. And then he emphasized it again. There was very little about them that were 'nimble', he said.
'Flexibility, self-service, speed-to-insight'. These are the fundamental elements of ‘Nimble Business Intelligence’, according to Seth. Given the reasons for BI project failures, these qualities would certainly help avoid some of those issues. One of the audience members seemed to violently agree when she called self-service the 'Holy Grail', lamenting that 'adding a column to a ResultSet for a BI app requires an entire spin through the waterfall SDLC'.
Seth emphasized that self-service means 'dynamic data access', 'visual' tools’ and ‘no ETL’, but also pointed out that the sources for these self-service solutions should be the same ones that feed the BI solutions you have today. Of course, I wholeheartedly agree that 'information agility' goes hand-in-glove with a self-service solution, like my buddy John Crupi recently wrote. Although Seth didn't say it, I expect one of the reasons for this is the ubiquitous IT backlog. 'Backlog' and 'agility' are archenemies, it seems.
Of course, Nimble BI isn't a panacea for all that ails BI. One savvy audience member asked about data quality and how Enterprise Mashups might fix or exacerbate that issue. Truth be told, Seth somewhat agreed, pointing out that 'bad data' certainly gets more common when you use open sources from the Internet. But mashups, he said, could be used to 'explore your data quality issues' and ultimately improve your data quality.
Toward the end, Seth gave a recap of what he believes enterprise mashups deliver, value-wise. I'll quote him verbatim, since I don't think I could say it any better:
Seth then concluded with a very important point: Enterprise Mashups do not replace BI solutions. They sit side-by-side, complimenting each other. Certainly, Enterprise Mashups can consume BI services and make part of mashup solutions. And the opposite is also true.
In the end, I left feeling that Enterprise Mashups perhaps deserve a place in the BI practioner's recipe book. The recording and slides from Seth's entire presentation are available on our Event archive. Seth has also written a bit of this topic, with a whitepaper on 'Nimble Intelligence: Enterprise BI Mashup Best Practices' and a blog asking 'Is It Time For NoETL?'.
Take a look, start thinking nimble.








