Overselling and under-delivering

Is “overselling and under-delivering” becoming a norm for the IT software industry today? This question would have diametrically divergent views depending on which side of the table you are sitting. Whereas clients would seem to nod their head in unison, but ask any IT software firm they would deny it vehemently. Being a part of the IT industry for quite some time now and however skeptical I may be of the clients, I have some reasons to partially agree with the strong statement made above. However, I believe much of the malaise can be attributed to the internal dynamics of the IT software industry.
The industry is replete with Death March projects. Some industry statistics suggest that almost 60-70 percent of software projects experience cost and time slippages. This is making fixed costs projects more popular with the clients as they are no longer willing to bear the brunt of the software vendor’s overzealous marketing and sales tactics. Time and material projects are a rarity today.

Intangible deliverables
The very name ‘software’ suggests that much of the attributes of the deliverables of the software industry is intangible and often difficult to quantify with numbers. Robustness, scalable, flexible are terms which are used with penchant in this industry. Often when an RFP (Request for Proposal) is prepared by the customer these loosely defined terms are frequently used to play safe, thinking they can be later used to squeeze the software vendors, but they don’t realize that they often backfire resulting in the bleeding project costs on both sides. The requirements of an IT solution is not adequately covered and open ended requirements are preferred thinking that these can be used to cover up any changes in requirements later on.
Project slippage
The IT software market is increasingly becoming commoditized. On the other hand, appreciating Indian rupee is putting pressure on the margins. This is often resulting in myopic attitudes by the sales and marketing team to bag new clients and customers. Often there is very little communication between the sales team and the delivery team and any threatening objections to the proposal by the delivery team is quelled at the very onset. Thereafter, once the project has been bagged, all responsibility falls on the delivery team to meet project deadlines and delivery costs. The sales team basks in glory and the delivery team sweats. If there is a slippage in delivery the whole blame falls on the project delivery team and little is done to bring the sales team under scanner for their shoddy estimates of the project delivery costs. Another important factor which contributes to the project slippage is our resistance to say ‘no’ to our clients and also to raise our voice against unreasonable demands made by them.
Lack of documentation
I have rarely seen a project which has very detailed documentation of the project’s various phases. We don’t like to do documentation, as cutting time on documentation can save costs. That is probably reflected in the documents we prepare as a part of our deliverable and also as a part of the internal monitoring process. Often client requirements are poorly captured during the initial study of any IT project. This makes any project extremely vulnerable during the later part of the project lifecycle when clients start getting a feel of the IT solution.
Poor quality of delivery
There are other reasons for poor quality of delivery by software companies. The quality of consultants is much to be blamed for this. Most IT companies are increasingly recruiting freshers to reduce costs and train them on projects. Thus consultants are being trained on clients’ expenses. However unethical it might seem but it is the hard reality. Inadequate scrutiny during the selection process often results in unscrupulous candidates being selected. Such is the pressure of recruitment that previously rejected candidates are offered jobs later on to meet the requirements of a depleting workforce.
Some of the projects are taken by companies just to gain a foothold in a particular domain or geographical area. In such projects profit is not the main object but without such profits in place, the delivery quality suffers subsequently.
Increasing offshore components of projects is also one of the reasons of why client requirements are not captured adequately. Regular client and end-user interaction is an important component in client satisfaction.

Anand Chatterjee explores the reasons why it so difficult to manage client expectations in the software services industry
For the complete article please follow the link:
http://www.expresscomputeronline.com/20071112/technologylife05.shtml
© Copyright 2001: Indian Express Newspapers (Mumbai) Limited (Mumbai, India).