Comments on: Get more out of your business intelligence solutions http://via.ie/cost-reduction/get-more-out-of-your-business-intelligence-solutions Business & IT Consulting Mon, 02 Nov 2009 17:26:52 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Kevin O'Callaghan http://via.ie/cost-reduction/get-more-out-of-your-business-intelligence-solutions/comment-page-1#comment-204 Kevin O'Callaghan Tue, 13 Oct 2009 16:04:28 +0000 http://via.ie/?p=442#comment-204 Hi Keith - Thanks for your comments and questions, some of which would cover many separate articles, but I'll endeavor to cover them here: 1 - Who would typically be involved in drafting a business intelligence solution/plan? At best, anyone who has a stake in the business intelligence solution should be involved. It is their data and their business rules that will ultimately determine the solution. Of course, in many organisations it is neither practicalbe to have every stakeholder involved, so you would doubtless require the business analyst to learn the rules of the business, represent the interests of the stakeholders and document these rules or requests in a business requirements document for the solution. The CTO or an Enterprise Architect would be involved as they would have influence on the solution being proposed as well as the type of solution that would apply alongside other IT systems.Doubless a project manager would be involved in getting the solution together which will eventually lead back to getting your stakeholders involved, at some point the new intelligence system will need to be tested and your stakeholders are a great resource in that testing. Keep them involved, just building a solution is pointless without their guidance - so where possible, involve as many relevant stakeholders as possible. 2 - Tools that help with the process There are many tools that can help document the process flow such as MS Visio. A quick google of processflow tools will highlight many. 3 - What sort of documents would normally be produced? Your call! Typically I'd err towards a business requirements document to document all the various business rules that are required in your solution. Get it documented and agreed. From an IT department, then you have functional specifications for a proposed solution. Think of it as a normal project within your organisation and find the most appropriate document format to get those business rules in writing - and then make sure they're all agreed! Hi Keith –
Thanks for your comments and questions, some of which would cover many separate articles, but I’ll endeavor to cover them here:

1 – Who would typically be involved in drafting a business intelligence solution/plan?

At best, anyone who has a stake in the business intelligence solution should be involved. It is their data and their business rules that will ultimately determine the solution. Of course, in many organisations it is neither practicalbe to have every stakeholder involved, so you would doubtless require the business analyst to learn the rules of the business, represent the interests of the stakeholders and document these rules or requests in a business requirements document for the solution.

The CTO or an Enterprise Architect would be involved as they would have influence on the solution being proposed as well as the type of solution that would apply alongside other IT systems.Doubless a project manager would be involved in getting the solution together which will eventually lead back to getting your stakeholders involved, at some point the new intelligence system will need to be tested and your stakeholders are a great resource in that testing. Keep them involved, just building a solution is pointless without their guidance – so where possible, involve as many relevant stakeholders as possible.

2 – Tools that help with the process
There are many tools that can help document the process flow such as MS Visio. A quick google of processflow tools will highlight many.

3 – What sort of documents would normally be produced?
Your call! Typically I’d err towards a business requirements document to document all the various business rules that are required in your solution. Get it documented and agreed. From an IT department, then you have functional specifications for a proposed solution. Think of it as a normal project within your organisation and find the most appropriate document format to get those business rules in writing – and then make sure they’re all agreed!

]]> By: Keith Farrelly http://via.ie/cost-reduction/get-more-out-of-your-business-intelligence-solutions/comment-page-1#comment-202 Keith Farrelly Mon, 12 Oct 2009 00:55:50 +0000 http://via.ie/?p=442#comment-202 Hi Kev, Very interesting, have a few questions. Who would typically be involved in drafting up an intelligence solution plan/design? Is this a CTO, Business Analyst or Enterprise Architect (or all of these)? Are there any tools in particular that can help with this process? What sort of documents would normally be produced? Keep up the good work! Keith Hi Kev,

Very interesting, have a few questions.

Who would typically be involved in drafting up an intelligence solution plan/design? Is this a CTO, Business Analyst or Enterprise Architect (or all of these)? Are there any tools in particular that can help with this process? What sort of documents would normally be produced?

Keep up the good work!
Keith

]]>