Estimation Should Not Be Accurate Less Is More
I’ve spotted interesting psychological aspect in estimation process. Colleagues did not want precise estimation. They wanted smaller estimation.
For example, if you estimate 100M $ and realization fails to perform planed figures. It is 97M $. Your calculation included experience factor, seasonal correction and estimation formula
Continue reading Always Plan Less [...]
How we know that company Information System is outdated and that it needs major upgrade or change with advanced systems?
Continue reading Saturated Information System [...]
Habit of code re-usage in Information Systems affects reporting consistency and makes significant impact on data quality. It is so easy to recycle code, but is it really necessary…
Continue reading Code Re-usage [...]
Here are several common mistakes made by data stewards and that might endanger data flows. Be careful about dates. Dates have to fit tightly to closing dates otherwise calculation of revenues or costs might break down. They cannot reference to historical or future dates, they have to match exactly to closing dates in
Continue reading Data Steward Mistakes [...]
Business Model Calculations Based on Allocation Keys
Many times business analysts in lack of data from source systems create allocation keys and make estimations, reports, analysis or business cases. Many times allocation schemes are not set up properly and only show lack of knowledge of coordinators who calculate required cases. If the allocation schemes
Continue reading Business Model Calculations and Redistribution [...]
Business Intelligence Reporting Trap
It is not always wise to recreate reports from source systems in Data Warehouse. Chances are that you’ll make much more efforts and engage more resources to create report in DWH instead to make it in source system.
In order to recreate required report in Data Warehouse all data need to imported.
Continue reading Replacing Reports from Source Systems [...]
Data Warehouse is not imune to changes on source systems, actually it is very vulnarable to them. If source systems have duplicate figures, Data Warehouse will also report duplicates. Here is an example from practice where guys made patch on CRM system to handle “urgent” marketing product without making any kind of communication toward reporting – DWH and Business Intelligence. Duplicated figures were in official reports for three months and caused significant deviations of core Key Performance Indicators. Unfortunatelly, reporting mistake was presented to the board members as Data Warehouse error.
Continue reading Business Intelligence Example of Reporting Errors – Duplication of Figures [...]
Business Intelligence Testing period can be very stressful for users who are not skilled with information. They can suffer from various types of doubts.
Continue reading Business Intelligence Testing Acceptance Fear [...]
If somebody makes change somewhere in production system, master data management or data warehouse there is a huge possibility that someone’s information functionality will be changed. We are all part of big information network and we have functional overlapping almost in all segments of business. Our work on information systems as IT developer, business analytics, data steward or decision maker (as methodology expert) affects many Information Systems participants. You can not act as lonely and isolated island
Continue reading Information System Functional Overlapping [...]
Choosing for example between 50 reports, and what needs to be developed might seem simple, but… Budget is enough for only 20, to pay to vendors, and rest should be somehow replaced with processes, negotiations with users and their bosses and with own deployment. Whatever you do, it is not your decision how will budget be allocated. Decision is more in hands of those who have better
Continue reading Limited Business Intelligence Budget Problem [...]