Skip to main content

Creating a responsive BI service

We're looking at how we can create a reporting and analytics service that can respond quickly to new requests for information.  The motivation for this is that business intelligence requirements change quickly; managers and data analysts frequently come up with questions for which they require access to new data in order to answer.

Many organisations have a dedicated BI team who can concentrate on the needs of their data analysts and other users. The most effective BI teams - by which I mean those teams who provide the most useful information to the people who need it - are multi-disciplinary teams that include business users, data analysts, data architects, and ETL developers.

Unfortunately, our current structure hinders this integrated approach.  We don't have the resources to dedicate a team to each of our services, because we run over 100 application services.  Instead, we have development teams and a support team, and a planning process that lets us assign staff effort to the most valuable or essential projects that arise each year.  It's efficient in terms of optimising effort for outcomes, but it is not an agile system.

Much of the IT industry is moving to a DevOps model, in which development and operations are combined.  That approach is usually found in organisations that develop a small number of products and so can afford to dedicate teams to specific services.  It would be a challenge for us to adopt this operating model across the board, but we think we can take some steps in this direction for the particular case of the BI service.

As a first step, we may create a virtual team, with the team members having a defined amount of their working week assigned to the BI service.  With this dedicated resource, we would put a process in place to receive and prioritise requests, working with senior management to set overall priorities.  This should enable us to respond to request from our BI users considerably quicker than our current processes. 

We are still at the early stages of setting up this service and many details will be need to be resolved before it is up and running.  There are no guarantees that we will be able to create this service within the constraints of the wider organisation, but I am optimistic that we can make this work.



Comments

Popular posts from this blog

Project Leadership

When I look back over recent projects that I've been involved in, it seems that one key to making a project successful is having someone on the team who really drives it forward: someone who is invested in the project as a whole and not just their own part in it. We (by which I mean the University's Applications division) have a well-defined project process, with defined roles, required milestones, deployment standards, and so forth.    All these are useful, but if the team doesn't have a leader, it seems a project can lose its way, perhaps not responding to changing circumstances, getting stuck on a technical problem, or not securing a needed resource in time to meet some external constraint. The leader can be any member of the team - it could be a developer, a project manager, or the sponsor, or someone in another role.  A team can include several people who are this committed to the project; it doesn't have to be a single person.   As an example, one of...

Business Model Canvas

A Business Model Canvas is a tool for mapping the core functions and capabilities of an organisation.  Compared to the Core Diagrams that I described in an earlier post , the business model canvas attempts to present more aspects of the business, starting with the value proposition – a statement of what the organisation offers to its users (in the business world, to its customers).  It shows the activities and resources, as Core Diagrams do, but also shows user relationships & channels, and also benefits and costs.  I’m not aware of any universities that have used this tool but you can find examples from elsewhere on the web. We are considering business model canvases as a tool for mapping the strategic capabilities of units at the University of Edinburgh.  Phil Taylor, our EA contractor, sketched an outline of what a business model canvas might begin to look like for HR: This is only intended to be suggestive: the real canvas would need to result from in-de...

"That's not Grid!" - A cautionary tale

I don't usually attempt humour here, but see if you like this... Once upon a time, in the far-off world of Computerland, a great guru arose and declared a vision. "I see a future when all computers will be linked together and people will run their programs without knowing which computers are running them. People do not need to know where their jobs run; they just need the results. I call this Grid Computing!" The people of Computerland were excited by the guru's vision. They went away and worked to make it happen. When they were ready, they returned to the guru and said: "Oh great guru! We have implemented your vision. We can run our programs on whichever processor is free at the time, making sure that all programs can run and making best use of all our processors. No longer does one computer sit idle while another one is overloaded. Your vision is a great success!" "No, no, no!", said the guru, "That's not Grid!" The guru exp...