Waiting for Business Intelligence Storm

Each company resolves tasks according to internal procedures. For updating, editing or changing Business Intelligence solution there is always handling procedure with list of Requests for Change (RfC) initiated by customers from different business areas. Each RfC has activity status. It is weird to see list of RfCs with action points for business who initiated RfC and to see it constantly in same status of inactivity. For example, business needs to make additional specification or to make prioritization of own requests but does not send any reply toward BI implementators. In other words, business customers ordered changes but do not actively participate in their implementation and act like not interested. 

There is a very common reason behind such behavior of internal customers. It seems like they have forgoten own claim. Business customers are more then ever forced to initiate requests but do not reserve internal resources for active participation in implementation. Without feedback in form of additional specification, problem solving activities on process level, making priorities between own requirements and similar, IT will not deploy requested functionalities. Requests for Changes will stay in pending status.

Pending status means unsolved requests will be permanent threat for developers like storm clouds. Storm is approaching but still did not start to act, requests are accumulating and waiting escalation through executives or board members to smash toward deployment at any time. With escalation (pleasant or unpleasent) deployment will have to immidately deliver huge amount of BI functionalities and reports.

Related posts, articles and documents:

• How to make Business Intelligence MasterpieceHow to Make Specifications for Business Intelligence Reports
• How to Start a Business Intelligence Project