Emerging Trends in BI

Recently TDWI and Forrester Reserach have come up with their views on most emerging trends/ Top prediction in Business Intelligence area. It is really intersting !! There are some commonalities and some differences which is obvious. TDWI has tried to pack all the things in 5 buckets , however Forrestor choosen for 10. 

My Idea for this blog is to provide summary of Both of the reports followed by my analysis and in last providing my vision. It goes without saying that both of these organization and person involved in research are experts in respective area. My intention is not to contradict however to provide my view point and coming up with my consolidated version based on my vision. For more details , I would suggest you to please refer to Information management/ Forrestor research and TDWI website:


Following is the summary of TDWI and Forrestor's reports.

Forrester Predictions Analyis

Boris Evelson(Forrester research) did a good job by touching all the important aspects like Self service , Cloud, Mobility, In Memory DBMS , Big data etc. However I feel that putting these items in 10 is little bit much and this could easily been squeezed to 8 points. If we have a close look on 1st and 2nd item, both seems to be same: the indication is in order to meet functionalities the diversity of tools will remain. Also 3rd and 4th point can easily be clubbed into one as the essence is: for empowering Business Self service BI plays important role. 

May be Boris wanted to touch upon some other aspects by keeping these points seperate , however, the exact context is missing some how, at least as per my knowledge and understanding. Also other important trends like sentiment analytics, Social media analytics and Advanced Data Visualization are missing too.    

TDWI Emerging Trends Analysis

David have highlighted very important aspect of UIA ( unified information access ) which I believe is the key driver for enablement of Self service BI. I am not sure why Big data trend seems to be restricted only for Social media, however this is already existing in industries having generated from other sources(refer to Phillip Russom report on Big data on TDWI websie). I feel,  Cloud BI , Mobility are really in and vendors also are playing very high on these too, somehow these are under highlighted.

My 2 Cents

I feel all of the important aspects/points can be consolidated with in 7 points, and after adding the missing Data visualization point, the final list becomes 8. 

regards : Ajay

5 reasons: why Indian System Integrators are not successful in Japan??

Why do Indian System Integrators(SIs) fail in Japan?? Failure in terms of growth as well as in profitability despite being present in one of the biggest IT market. And the most astonishing fact is most of the SIs are present in this market for more than decade, however still struggling to find Golden key to success. And somehow Japanese IT companies and major Global IT players profitable !!

Recently I had been intrigued by this question again and again. Therefore out of my curosity I did some research, deeper thinking to recall my experiences and spoke to variety of people involved in this industry. Then according to my understanding,I came up with five most important failure reasons which are very important for any Vendor to understand and work upon in order to survive in this geography.. 

1) Operating Model

US being the major source of revenue for almost all the major Indian SIs therefore the operation  models of these SIs are usually drafted based on lesson learnts in US geography. If we see, practically all the  vendors have one uniform model (i.e. how Marketing, Sales, Delivery are going to operate etc) which is inherited from bigger US based model and enforced on all geography. This works in some geography like Europe, ANZ where the working culture as well as the process maturity is more or less same as US. However when it comes to geography like North Asia, ASEAN , this model start falling like deck of cards.In another words Indian SIs are trying hard to prove the impossible " one shoe fits all ".  As usual , exceptions /miracles do happen so in these geography too there are some. This is very tricky as it creates a delusion that success is possible and on other side doesn't give exact exit point. 

Lets try to see Japanese IT prospective market . There would be following categories a) MNCs operating in Western style b) MNC operating in Japanese style c) Local Large Enterprises operating in Orthodox way d) SMBs operating mostly in orthodox way and e) Govt sector working in orthodox way. 

By looking at above , we can easily find out that out of six categories, the Indian SI vendors are successful primarily in first category , others are more or less hit and trial. Why hit and trails, failures, simple reason is uniform operation policy doesn't fit other 5 categories. So there has to be lots of thinking done to come up with operating model suiting this geography.  

2) Resources

Once we have operating model in place we need to think about the people who are associated to make this successful. Its a common belief that company can survive in this market only if it has adequate natives onboard as well as EXPATS with bilingual skills. I would say this may not be true for all the aspects of Operating Model. In my experience , it sometimes , creates huge Abyss between different bodies of organization, which instead of working together in synchronization, work differently , causing waste of energies and finally changing the course of direction or progress is stalled. Some examples may be gaps between delivery and sales, sales and marketing , country manager and Sr. management etc.

Most of the organization think that the resources are like Lego blocks and these can be put in any condition with any other blocks and they will absolutely fit in, however little do they realize that there are dealing with human beings who hail from different cultures, have different though process and different behaviour.Therefore its not easy , rather impossible to gel these pieces together. Usually the most common debate is: Native feels Expat don't understand the culture and Expats feel that Native don't understand the soul of organization. So you can very well make out where the things are heading...

This is the second most point to fix. For being successful , one needs to achieve Synergy where all small forces work in one direction towards the growth. So the key is to put the right skilled people at right place at right time. This is easily said than done. This requires lot of maturity and for sure some calculated hit and trails.  

3) Project execution Model

After laying down the correct processes and identifying right set of people, Vendors need to take a deeper look on how the projects are executed. The projects are usually having two types of models ( T&M and FB) . Its been seen that almost all of the FB projects tend to end up in Red. Really Interesting !!
  
To start with all the project start as if Vendor - client match was made in heaven , every thing looks perfect and harmonious however things start turning sour soon when the milestones dates draw nearer. Why, is so? Don't we have good plan ? No that is one of the factor , however, there are  lots of cultural and process related reasons or catalysts which changes the color of relationships.These are as follows :

a)requirements are not frozen b) Escalation doesn't work at all .Because there is usually a team who makes decision so that no single person is made accountable. c) Projects are executed in T&M way d) Vendor doesn't allocate the right team to project etc etc.

Interestingly , most of the Japanese IT vendors realize this fact and execute the project in T&M or T&M with cap model and in worst case if they execute FB with economic adjustment. That is why they are very successful .However Indian Vendors are under so much pressure to follow uniform operating model and to provide non existent value, fail to understand a simple fact.  This sometimes is little difficult to achieve while working with MNCs client because they are better manager of risks and usually are driven by HQ policies. But still the decision to take it or leave is with the Vendor and must be taken based on operational  strategy.

4) Costing Model

Now we understand the eco system to some extent, however without having good  costing model, its not possible to get more business. Now If we have a close look, the costing model too is driven from uniform operating model. This usually is impractical as I have never seen any regular wins in line with the prescribed rates. In another words the rates being maintained by Indian IT vendors are too high. Since these are high and the market expectations are less , this create a gap. And here it introduces unnecessary communication overhead to take approvals for closing the deals. Also in many instance client doesn't feel having any advantage if compared with Top 5 Global SIs . For sure if the services provided are same and the there is no marginal difference in cost then why Japanese companies will opt for Indian Vendors?

Now if we look at the reasons, why this cost is higher, there can be many reasons. First its defined based on some other geography and second is because of the higher resource cost due to insistence of Bilingual skills. Most of bilingual resources are paid as good as expats , in many cases much more than bilingual. This makes the profit margin less and leaves a very less space for adjustment.

For first one, probably the IT companies need to have a close look of the market. One can easily get onsite Chinese resource with Japanese skills at around offshore rate quoted by Indian vendors. For second one , I believe its not at all required to have bilingual skills at all the level. Just composing a team with strong bilingual leader/s who know the IT vendor working philosophies and cheaper resources at lower level will do the trick. This can reduce the the over all cost providing desired operating margins and enhancing the winning chances.

5) Mis reading Culture and Lack of Persistence

Japanese companies operating in orthodox way are usually too closed , not open to any change and like to work prevailing situations with proven networks. This makes the ice breaking very tough at first instance and even once its done the results received are usually very very small to start with, this is where the Indian Vendors loose patience.

I have seen the usual selling cycle of 1-2 years for just couple of resource augmentation. This surely requires lots of follow ups, relationship nurturing in order to reach that state. However sometimes when this state is reached the Vendor is not having the right set of resources and rather just pushes whosoever is free. This makes the situation worse and creates the direct impression of Vendor Capabilities. 80/100 of these cases are closed and never open. The remaining cases where the right resources were allocated , make the account asset for any Vendor. 

Being a closed knit small community , world of mouth travels faster than any thing else. So , Networking/relationships, good work ( world of mouth) , patience is very very important. So the Key is to have lots of these opportunity ongoing and keep on following up and definitely be ready with right Resources. 


To Summarize, we can see that there is a lot of work needs to be done in order to be successful in this geography, this usually will start from changing the perception altogether and aligning operating model in line with Japanese Business culture.Indian IT vendors are just part of service based industry so this simple fact needs to be realized. One needs to work on right resources, right costing model and choose the right execution model in order to be successful in this geography. 

Hope the above given some hooks to catch. The above is purely my thought process . For sure there would be some other ways too...  

Project/Program Management Extra Steps series, Part 2

Due to many festivals , I couldn't take out time to write further. Anyways ..Wishing you all Happy Diwali, Happy Halloween ..

Continuing further on the Extra Steps series, lets talk again on communication management. Again to say , this is one of the most important plan for any project. And most important aspect of any communication management is to know about stakeholders. Please remember the Golden rule : For any project successful, it is implicit to have the right information flowing to right stakeholders at right time.

As we know  IT projects has variety of stakeholders, ranging from Business department( key driver and system users), IT department and Vendor( for build ) and Operation dept( for application maintenance and post go live operations). This itself is complex and if we add some other aspects like multiple vendors ,different locations/timezones, different culture and languages, this become super complex . One can image how important is communication management in above scenarios as there would be many many communication channels. The simple formula to find out number of communication channel is as follows

Number of Communication Channel = N (N - 1) / 2

Usually we create wonderful plans which looks great on papers however falls flat when it comes to actual implementations. There are various reasons , I am just quoting few of those as follows which I feel most important .

1. Identification of all the stakeholders who has direct and indirect influence. Usually our plans are around the stakeholder who have direct involvement in project and we miss out on those who needs to be just informed.
2. For the identified stakeholders , the practice is not to capture the required satisfaction level for separating important stakeholders from regular ones. This alone can make or break the project.
3. There is no dedicated stakeholder delight measurement practice. we just measure it with project deliverables . However this may or may not work.
4. Other points are governance flaws which I am not intending to discuss. 

Now lets see what Extraa steps can make the project more successful

Togaf ( The open group architecture framework ) provides a beautiful way of capturing stakeholders interest, involvements , power. This surely can help project team to have focused  and effective communication. Just have a look on following sample( this surely can be tailored based on project needs, the views and view points are more in relation to Enterprise architecture ): I believe having a good stakeholder map takes care of 2nd point.

For the first point , the Project manager and team needs to keep ear and eye open during all offline discussions with non project members( usually from client Business , IT and Operation departments). PM needs to decide based on discussion with core team members to include their name in Stakeholder map or not. It can also happen that project team maintains internal version for maintaining the additional stakeholders for not to missing out expectations. Ideally we should have only one version( to avoid any version mismatch and other issues) , however it depends on political situation of project.

For third point , the communication plan should have provision and bandwidth for stakeholders survey. Ideally this can be done by team other than project team or by Senior Project members. Project manager should sell this to stakeholders during approval of communication plan. This practice usually gives different forum for stakeholders to raise their concerns and most of the times intent is for project success.

I sincerely hope that implementing these small extra steps would bring success to your projects.


regards 

Ajay

Cloud BI

Cloud , cloud every where .. Don't you think so ? In case not , you will see it soon . Atleast I am in clouds now a days :). 

Day before yesterday I was listening to Marc Benioff ( CEO of Sales force ) key note address during Dream Force 2011 and panel discussion with Eric Schmidt( Executive Chairman of Google). I was amazed to feel their energy ,passion and future vision. No doubt , the Cloud is the turning point of IT industry , the last one we had during Mainframes to client server transition. As things are evolving so there would be mixed responses during this phase. Some will say , this is a bubble and it will burst soon. Who cares , though I am in clouds , but i can see very far :). Post that I listened to some old keynotes of Steve Jobs, Mark Zuckerberg , Larry Ellison and concluded that all are pointing in one direction.

So..I am very excited to be part of this transition and see how quick things will be adopted. They say , Every disaster has an opportunity hidden. To relate this I would say the current economic situations are acting as catalyst to strongly push cloud market. Also I am equally excited to see what changes this transition will bring to BI industry, how BI will fit in, how the future BI architecture look like?? 

There are numerous advantages Cloud offers, the major are Time to market and economic ( initial cost as well as Total cost of ownership). The other ones are better performance ( subject to architecture) , scalability , almost no upgrades overheads and so on..

Now its lot about the trend and benefits, Its time to have some basic understanding of Cloud computing? Wikipedia definition goes like this:

Cloud computing is the delivery of computing as a service rather than a product, whereby shared resources, software, and information are provided to computers and other devices as a utility (like the electricity grid) over a network (typically the Internet).

In simple words its just moving computational power from on premise to cloud in Internet and accessing this computing power by web browser/web services etc.  Vendors are offering three kind of flavors

1. SaaS : Software as a service . e.g. Sales Force
2. PaaS : Platform as a service. e.g. Microstrategy cloud
3. IaaS : Infrastructure as a service. e.g. Amazon EC2

Talking about BI in cloud , I feel most of the would fall in PaaS(Platform as a service) where vendors provides world class hardware and Software strictly in line with BI requirements, be it DWH appliance, Data integration tools, Reporting layer etc. Also Companies can immediately start developing /deploying on these world class environment offering wealth of tools. E.g. Microstrategy Cloud offers Microstrategy suite on reporting layer, Netezza as DWH appliance and Informatica for Data Integration.

IaaS ( generic cloud ) is also be used by some of organizations , however this might throw additional tasks like platform setting up, tuning etc to inhouse team. Amazon EC2 , database.com , Azure are leading examples in this category.

We can also see some companies opting for third party BI applications on SaaS. e.g. Sales force appexchange offers thousands of applications and hundreds of consulting partners.

Effectively we can see BI foot print would be there on all three flavours.  
 
Some Points to take care

1. Proof of concept is highly recommended prior to overall change. This will help to set expectations, benchmark etc.Lot many vendors offer free trial, FYI.
2. Please check the data policy of your organization as some of the organization would not like to have the data stored outside the company firewall.
3. Performance can take a hit , If cloud architecture involves accessing data from on premise. 
4. Ensure adequate Security measures for data access and storage in multi tenancy environment as well as cloud accessing on premise data. Do thorough due diligence with while selecting a vendor and during POC phase.

So Cloud is a way to go .. Guys gear up.. Happy clouding:)..

regards, Ajay

Data Integration Series part 1 : Data Replication/Synchronization

Whenever we come across terms " Data Replication " & " Data Synchronization" , our brains start painting pictures of different databases, their inter-connections, data volume / frequency etc. This is a very interesting field as one can feel the data flowing in organization. Its more or less setting up and maintaining nerves/veins system of any organization. Personally , I have been fascinated by Data integration techniques since start of this century when I was responsible for managing multiple DBMS in different locations. 

Indeed these terms are around for quite some time, however with time and growing business and IT demands, there are lot many changes happening. In this blog (which is the first one in the data Integration series) lets try to understand what is the meaning of these terms, approach, usage/use cases , trend and important consideration etc.

Definition/s:

Data Replication : This is the process of sharing information so as to ensure consistency between redundant resources, to improve reliability, fault-tolerance, or accessibility.( Source : Wiki). The above definition sounds very generic and almost complete as this covers most of important aspects of data Integration. If we add the direction part to it then I believe this becomes complete. When I say direction , it is usually data source to destination/target i.e. one way only. We will talk more about direction in Data Synchronization . One caution , Like others technology area, this too is evolving fast so you might come across numerous definition versions.

Data Synchronization: This is the process of establishing consistency among data from a source to a target data storage and vice versa and the continuous harmonization of the data over time( Wiki). This is mere extension of Data Replication or can also be called  Advanced Data Replication. To understand better, just visualize, data replication happening between resource A to B and B to A so that both the data sources A & B are synchronized.

Implementation Approach/s: There are are various ways to implement Data replication. I feel these fall under following two categories

1. Direct approach : Using Data base Tables directly by using SQL or tools
2. Indirect approach :Using logs created by RDBMS in real time ( Change Data capture).

Both of above have pros and cons depending on the requirements. However the recommended approach is CDC(change data capture) since its in-obtrusive as this doesn't chock the Database server performance.Tools implementing CDC reads the logs generated by DBMS system/s and not on tables so no additional I/Os operations are carried out by DBMS system.

Usecase : Usecases of Data replication are for DW/BI and non-DW/BI purposes. As the name suggests the first one is for integrating DWH and for BI ( operational reporting, dashboards etc). The non DW/BI falls under application integration category e.g. 360 degree view of customer data. Also for another entities like product, reference data this is widely used.   

Trends:
External drivers like Increasing competition, shrinking economy has put organizations to strategize in terms of enabling Faster decision making, cost reduction and higher availability. So we can very well see initiatives are coming from IT as well as Business to meet company strategic vision. 

As per TDWI survey 17% are using real time DW functionality and more than 90% are committed to use in coming 2-3 years.So one of the biggest trend in realtime Datawarehousing and analytics. There are many many cases in BI/DW area which gets impacted by this , some of these are Operational BI, on Demand management Dashboard, Alerts and Notifications etc.

For non BI/DW, the biggest following trend is single view of Customer data integration, Product data , reference data and some other data entities.  And in order to have in-obstrusive and scalable implementations , organizations are opting for CDC ( Change Data Capture ) methodologies. Here comes Data Synchronization into picture because multiple applications / architecture are to be accommodated. 

Points to take care:

1. Understand 3Vs** of data ( Volume, Variety and Velocity ) requirements. Volume is about size of data. Variety is about the data type ( structured, un structured etc) and velocity is about frequency ( Batch, realtime etc).
2. Choose the replication tool with advanced Capabilities in order to cope with scalability by handling heterogeneous sources, conflicts aroused during Data Synchronization , alerts and Notifications etc
3. Document the interface specification( source and Target) clearly and keep it updated. This is mandatory as any small change in any source can create havoc.
4. Real time integration brings technical challenges and complexities, however also provides tons of opportunities for Business Analyst to see different dimension of data which was not experienced before.
5. Use the services of Data integration specialist is highly recommended. 

Resources :

1. TDWI webinar ' Data replication for DWH and BI ' by Phillip Russom
2. Wikipedia for Definitions

regards , Ajay

Legends
**  3Vs were coined by Philip Russom of TDWI in his Big data analytics research, however I think these beautiful terms can also be applied to any integration techniques

Project/Program Management Extra Steps series, Part 1

The objective of this series of blogs to talk about the extra step / out of box thinking /common sense/extra cheese topping used by Project, Program, Portfolio and PMO to make the dramatic change in situation. I would be taking up real life scenarios either experienced by myself or as I used as consultation to other programs.

Today being the first part of this series and I am taking up very interesting scenario which falls under Communication Management. We all know this is one of the most critical area as when we talk of IT projects, its mostly interactions with human beings.

Background : A large SI is executing projects for a APAC customer. The account is in category of 3P ( triple platinum ) indicating direct monitoring by Top management. Multiple projects(support, development, enhancement) are being executed and team size goes in many hundreds too.Teams comprising of diverse cultures and are operating from different geographies. There are numerous PMs/Prgm M governed/mentored by a team of PMO which is central to engagement. The relationship with client and vendor swings up and down. Also most of the team members are used to work under fire mode.

Scenario : Every week end, PMO collates a status report for top management. Delivery timings , content and quality of report is quite critical to this engagement. There are frequent audits carried internally by Client and any deviation with actual to reported status is treated a severe compliance issue and can lead to legal action against vendor. For collation, the practice is that PMO sends out mails to find out status from respective PMs. Last week one of the PM didn't not receive the mail because the PMO mistakenly used the old id ( email id for this resource was changed due to some issue).There was couple of follow up emails( mentioning very clearly that no response means , no progress during last month) on that, but these mails too were directed to incorrect ID. Please note PM is not at all aware of this as he is not receiving any communication.

Analysis : PMO is frustrated that there has been no response even after escalation and finally concluded that there was no progress during last month. On the other side PM is too busy with project and has taken for guaranteed that no communication from PMO means no status report this week. This resulted in a gap in reporting as project couldnot communicate a critical issue to Top management as well as it missed out to provide details of deliverables made in reporting week. Next week unfortunately the project was selected for client Audit and this gap surfaced out and loud. This made vendor situation very tough as it there were series of apologies. 

I believe these kind of situations are very common in large engagements(which requires lots of collaboration) or during the times things are on fine(the priorities are different). In above situation , seems like the communication plan was not updated, also not planned well during planning phase.

My 2 cents : Any mature Project management professional can propose numerous solutions  like to have updated communication plan, process for making sure plans are updated and communicated, strict SLA behind every official communication, central project repository , automation of status report creation etc etc. Above recomendations are  must from process point of view, however one can again caught up in situation like this. 

Now lets talk about the extra step , I believe, just a single call from PMO to PM could have averted this situation. These kind of extra steps requires very less physical effort however requires a big change of attitude. So guys, whenever responses are not as per expectations, dont just stick to what age old good process says, simply pick up the phone/ visit the respective person. This will surely make life easier and act as stepping stone for project success. 


regards, Ajay

Understanding Social BI

Social BI: Topic sounds interesting, isn't ? Lets discover this a bit. The idea of this blog is to understand what Social BI is and how corporates can feast on its power.

The term social networking would certainly make you think the way you are connected and contributing to this rising market.Why it is rising , lets check out the numbers involved in this. Till last month Facebook had over 800 Million users( indeed a whopping figure) and Google+ crossed 50 Million mark in short time. These are leaders, however there are many more which are more regional. The best part is these are growing exponentially. Not to forget numerous countess twitters, blogs etc. As per Pew research on usage: about 83 % of youth for age group of 18 to 29 yrs which almost doubled in last 2-3 years and to me more interesting is 50-64 yrs bracket with a growing rate of over 1000 times. You can very well make out that the numbers involved are huge and power driven by these numbers would be enormous too. From another dimension , we can look this as mammoth CRM system, where data is maintained by users themselves.

Now, lets understand the usage of Social networking media from different perspective. Most of us use it for entertainment, collaboration, connection , sharing, learning and for many other things. Basically what is been happening is we say or follow something , somewhere and somehow. Please note, this in totality generates  huge data.  This means opportunities to know in terms of what is going on in society or what is the sentiment right now. Just imagine, if we are assisted with some powerful tool, then we can easily analyse this sentiment and have business/marketing strategy tuned, if we are part of corporate. Have personal strategy defined being an individual and have political strategy in case of Govt. The potential is huge , very huge. To provide other side of it , in recent times we have experienced several incidents/causes all around globe which were driven by social media and at many places where Social Networking acted as Saviour, specially during Japan earth quake crisis and Irene Hurricane. 

Now we know the source of this data, however tapping it has its own challenges. Firstly there is no direct access , secondly the data quality. There are various tools and solutions available which we will talk about in later section. Firstly lets see how organizations / individuals can feast on this.

Out of above ,lets see one usage from Business perspective with market leader ( Facebook) . I believe , any Global organization, can easily comment Its the Facebook where the customers are :). To unleash this power, corporate are using three following ways;

1. By creating Fan Pages
2. Doing Target Messaging 
3. Creating applications.

Fan pages build ongoing dialogs, target messages helps with limited target advertisement however both are very much limited. However the third option delivers rich interactivity in terms of bringing targeted , personalized and relevant content directly to consumers. For example,  just think of receiving discount coupons, loyalty perks, special offers and services from your favourite coffee brand.( I would certainly like to get some of these from Starbucks ;)). The steps involved are , users installs the facebook application and commits to share data(comprising of Demographics,behaviours, likes and friends etc) to application owner for various purpose as mentioned in agreement. Consumer intelligence is carried out on application users data .Organization do data mining , come up with marketing strategies/ campaigns and its go on and on.

Above looks great and simple. For sure, however everything comes with a cost tag. Firstly one needs to have proper tools to have access of data by using permission tokens and provision to enriching this from demographics perspective as  many of the users don't fill out complete information e.g. town name is mentioned without state and there can be many towns with same name  , the siblings are incorrect etc. There are many tools available in market , however please mind that these are still evolving. To name a few Microstrategy ( wisdom and Gateway ) , Antivia, Lyza , Panarama Necto etc. Secondly the organization is able to understand the market trend by doing proper data mining and align this with marketing startegy. Thirdly get the feedback and keep on improving ..

My recommendations:

1.  Social Media/Networking is evolving and it indeed offers tremendous potential for Corporates , Individuals, Govt. sector to carry out consumer analysis, sentiment analysis etc. BI professional needs to understand the influence on BI.
2. Data is huge and growing , however the Data quality is of concern.
3. Tools are evolving as the market is . Few big and small vendors are already making their presence felt . Many more Heavy weights vendors are coming in or planning to come in join this growing market. Have a close watch on upcoming tools.
4. Individuals need to understand the data share agreement with application provider.
   Hope you all enjoyed this.

I plan to cover another important aspect of Social Bi(Sentiment analysis) and text analytics some time later.. 

Can BI projects be offshored and delivered successfully?

Recently I was hearing to thoughts of Krish Krishnan , who is renowned industry in strategy architecture and implementation of high performance DWH solutions. It was quite an interesting session as we all know that many of the BI projects stalls due to numerous reasons.I would not repeat the whole talk as transcript as you can refer to same in TDWI webinar section( Managing risks of offshore Data warehousing). I would provide some gems and end it with my experience managing such like engagements.

Krish made a very important point that DWH program is special and is unlike other software projects, how,

1. Its an evolving program because of ever increasing demand of business requirements. None of enterprise who have implemented DWH /BI solution can confirm that the in place DWH system/s doesn't need any changes. All are experiencing some changes happening at some point of time, be it on Reporting layer or Integration layer.


2. Its a very complex Program as it involves complex technology , multiple stakeholders, multiple SMEs, multiple applications, and ongoing development. Bringing all under one roof is indeed challenging.

In order to have successful off-shoring there are various critical factors(people, process and organization) which need to be taken care by project owner. First two are obvious, however I was interested to find organization , and that surely made sense to me in order to transfer risk ( for data , multiple locations etc) and exploiting cost( blended cost) and talent and proven process advantages one needs to put this as important factor too. All the above points are based on work balance between offshore and onsite as any imbalance can lead to risk of ownership issue, communication issues availability of resources etc which can be devastating. I feel , Krish was very particular about management of communication & expectations effectively.

To summarize: I feel most of things are common Project management chores except for complexities of collaboration and evolution of DWH with in and outside enterprise/s. For sure there is no silver bullet which fits all . There is a need to be patient to achieve the right maturity levels. based on my experience ,I have following points to offer.

1. At onsite, the program should have Right set of people to understand and manage stakeholders expectations( technical, political, ego , cultural etc). And offshore owners must be imparted this very knowledge seamlessly else the program would not be in one world, rather two , simultaneously coexisting with each other which never meet.


2. Its best to have single Program Manager not like a usual onsite and offshore owners. I feel puts additional overhead and delays decision as both onsite and offshore reports to one who is managing multiple such like programs , and its obvious that there would be some conflicts.


3. Focus on mix of team at onsite , this is very important when it comes to manage global, co located project have diverse cultures.


4. If working on newer technologies, please plan accordingly as this could be a tipping point.


5. Try to retain core team members if not possible, insist to have effective Knowledge transfer. I feel usually 80% of the tacit knowledge is gone waste whenever there is turn around.


6. If possible , arrange for onsite visit for all key offshore members and vice versa. This needs to planned smartly.

Cheers!

Starting this Blog

My Idea to start this blog is to contribute back to society on regular basis whatever experiences , learning I have been having specially in the field of Information management.


I would be contributing my personal experiences, my thoughts on other ideas trying to give several dimension to any aspect of Business Intelligence in addition to latest industry updates. I would be touching on various topics like, Business Intelligence, Business Analytics, Dashboards, DWH, Datamart, Data Integration, Cloud Computing, Project/Program management, Mobility , MDM, CDI, PDI , Data Quality etc. 


The world of Information management is so vast ,so mesmerising and fast evolving. There are numerous thoughts , best practices popping up to improve business decisions so that the businesses can be successful. How they can be ? Only if they have the right information available at right time and applied to right situation. This is where Information management help.


There have been numerous words floating around, like Information management, Business Intelligence , Business analytics , Data Integration etc. I feel Information management is the umbrella which covers all the aspects like how data is managed, privileges to take out information from raw data at will and applying this to help take better decisions.

Welcome you all to my Blog . Hopefully , my passion would surely help me to be regular at least on weekly basis if not daily.


God Bless all!